| 2 |
Meeting agenda, arrangement, and meeting report |
|
| R4-2503100 |
RAN4#114 Meeting Report |
ETSI MCC |
| R4-2503101 |
Agenda for RAN4#114-bis |
RAN4 Chair (Huawei) |
| R4-2503102 |
RAN4#114-bis Meeting Arrangements and Guidelines |
RAN4 Chair (Huawei) |
| 4 |
Incoming LS |
|
| R4-2503103 |
LS on Rel-18 RAN1 UE features list for NR after RAN1#120 |
RAN1 |
| R4-2503104 |
LS on Rel-19 RAN1 UE features list for NR after RAN1#120 |
RAN1 |
| R4-2503105 |
LS on measurement quantities for IoT NTN |
RAN1 |
| R4-2503106 |
Reply LS on CSI-RS measurement with SBFD operation |
RAN1 |
| R4-2503107 |
Reply LS on Ku band numerology |
RAN1 |
| R4-2503108 |
LS on L1 based UE-to-UE CLI measurement and reporting |
RAN1 |
| R4-2503109 |
LS on TDM DMRS for 3.75kHz SCS OCC |
RAN1 |
| R4-2503110 |
LS on the wake-up delay for LP-WUS operation in IDLE/INACTIVE mode |
RAN1 |
| R4-2503111 |
LS on time location of on-demand SSB for SCell |
RAN1 |
| R4-2503112 |
LS on Rel-19 higher layers parameters list Post RAN1#120 |
RAN1 |
| R4-2503113 |
Reply LS on AdditionalSpectrumEmission |
RAN2 |
| R4-2503114 |
Reply LS on LP-WUS subgrouping |
RAN2 |
| R4-2503115 |
LS to RAN4 on granularity definition of pdcch-RACH-AffectedBandsList-r18 |
RAN2 |
| R4-2503116 |
Reply LS on LP-WUS operation in IDLE/INACTIVE mode |
RAN2 |
| R4-2503117 |
Reply LS on SSB adaptation |
RAN2 |
| R4-2503118 |
Reply LS on Ku band numerology |
RAN2 |
| R4-2503119 |
Response LS on simultaneous operation between GNSS and NR NTN |
RAN2 |
| R4-2503120 |
Reply LS on UE capability for FDD-FDD inter-band CA simultaneous Rx/Tx |
RAN2 |
| R4-2503121 |
Reply LS on L3 measurement based LTM support over F1 |
RAN3 |
| R4-2503122 |
LS Reply on Parameters for 14800 to 15350 MHz of terrestrial component of IMT for sharing and compatibility studies in preparation for WRC-27 |
RAN |
| R4-2503123 |
Reply LS on L3 measurement based LTM support over F1 |
RAN |
| 5.1.1 |
Main session |
|
| R4-2504659 |
Topic summary for [114bis][101] R19_UERF_maintenance_TEI |
Moderator(Huawei) |
| R4-2505220 |
WF on UL Tx switching for TEI19 |
MediaTek |
| R4-2505221 |
LS on UL Tx switching for TEI19 |
MediaTek |
| R4-2505222 |
WF on PHS protection update |
KDDI |
| R4-2505232 |
WF on Introduction FR2 Power Class 8 |
Huawei, HiSilicon |
| 5.1.3 |
BDaT sessoin |
|
| R4-2504626 |
Topic summary for [114bis][301] BSRF_Maintenance_TEI |
Moderator (Ericsson) |
| R4-2504644 |
Topic summary for [114bis][319] Demod_Maintenance_TEI |
Moderator (Nokia) |
| R4-2504652 |
Topic summary for [114bis][327] OTA_Maintenance_TEI |
Moderator (Keysight) |
| 5.2.1 |
Introduction of the 1.4 GHz Band |
|
| R4-2503490 |
draftCR to TS 38.104 on sync raster correction for band n110 |
CATT |
| R4-2503491 |
draftCR to TS 38.101-1 on sync raster correction for band n110 |
CATT |
| R4-2505218 |
draftCR to TS 38.104 on sync raster correction for band n110 |
CATT |
| R4-2505219 |
draftCR to TS 38.101-1 on sync raster correction for band n110 |
CATT |
| 5.2.4 |
Introduction of NR band n68 |
|
| R4-2503513 |
Draft CR to TS 38.101-1 - Correction of A-MPR tables for band n68 |
Qualcomm Technologies |
| 5.2.7 |
Others |
|
| R4-2503162 |
Draft CR to TS 38.922 on corrections and clarifications on IMT parameters |
Nokia |
| R4-2503480 |
CR to TR 38.922 on power dynamic range |
CATT |
| R4-2504265 |
Draft CR to TR 38.922 Removal of references to internal TRs and Tdocs |
Ericsson |
| R4-2504266 |
Draft CR to TR 38.922 Addition of AAS BS spectral mask and spurious emissions for 14800 to 15350 MHz frequency range |
Ericsson |
| R4-2505213 |
Draft CR to TR 38.922 Removal of references to internal TRs and Tdocs |
Ericsson |
| 5.3.1 |
UE RF related topics |
|
| R4-2503175 |
On the proposed FR2 PC8 (new power class) UE |
Qualcomm Incorporated |
| R4-2503272 |
(TEI18) DraftCR on 38.101-1 clarifications on special sync rasters for n100 [Sync_raster_3MHz_n100] |
Huawei Technologies France |
| R4-2503273 |
(TEI18) DraftCR on 38.101-1 clarifications on special sync rasters for n100 [Sync_raster_3MHz_n100] |
Huawei Technologies France |
| R4-2503562 |
n1 NS_05 and NS_05U PC2 A-MPR proposal |
Qualcomm Incorporated |
| R4-2503717 |
(NR_newRAT-Core) Further study on NR A-MPR reevaluation scenarios on n1 for Japan |
KDDI Corporation |
| R4-2503826 |
Draft CR to 38.101-5 on UE channel bandwidth for FR2-NTN |
vivo |
| R4-2504078 |
Introducing Tx switching for 3Tx UEs in Rel-19 TEI |
MediaTek Inc., Orange, T-Mobile USA, Vodafone, Verizon |
| R4-2504079 |
CR 38.101-1 on time mask of Tx switching for 3Tx UEs [3TxSwitching] |
MediaTek inc. |
| R4-2504164 |
(NR_MC_enh) R18 correction of switchig time between NUL and SUL carriers |
OPPO |
| R4-2504165 |
(NR_MC_enh) R19 correction of switchig time between NUL and SUL carriers |
OPPO |
| R4-2504166 |
R16 n1 NS_05 PC2 AMPR |
OPPO |
| R4-2504167 |
R16 n1 NS_05U PC2 and PC3 AMPR |
OPPO |
| R4-2504180 |
Discussion on introducing Tx switching for 4Tx FWA |
Huawei,HiSilicon |
| R4-2504184 |
On the options proposed for PC8 |
Ericsson |
| R4-2504322 |
Discussion on introduction of FR2 PC8 |
Huawei, HiSilicon, CTC, CEPRI, OPPO, vivo, Xiaomi, CATT, Spreadtrum, Google, Honor, TD Tech, StarPoint, SRTC |
| R4-2504323 |
CR on introduction of RF requirements for FR2 PC8 in TS 38.101-2 [FR2_PC8] |
Huawei, HiSilicon, CTC, CEPRI, OPPO, vivo, Xiaomi, CATT, Spreadtrum, Google, Honor, TD Tech, StarPoint, SRTC |
| R4-2504324 |
CR on introduction of RRM requirements for FR2 PC8 in TS 38.133 [FR2_PC8] |
Huawei, HiSilicon, CTC, CEPRI, OPPO, vivo, Xiaomi, CATT, Spreadtrum, Google, Honor, TD Tech, StarPoint, SRTC |
| R4-2504325 |
CR on release independence for FR2 PC8 in TS 38.307 [FR2_PC8] |
Huawei, HiSilicon, CTC, CEPRI, OPPO, vivo, Xiaomi, CATT, Spreadtrum, Google, Honor, TD Tech, StarPoint, SRTC |
| R4-2504326 |
LS on introduction of FR2 PC8 |
Huawei, HiSilicon |
| R4-2504558 |
(PHS_System_NRonly) On the requirements of modifiedMPR-Behavior |
Huawei, HiSilicon |
| R4-2504569 |
A-MPR regions for NS_05/NS_05U and optionality in earlier releases by modified MPR behaviour |
Ericsson |
| R4-2504570 |
Draft CR to 38.101-1: Modification of additional requirements indicated by NS_05/NS_05U |
Ericsson, Samsung |
| R4-2504571 |
Draft CR to 38.101-1: Modification of additional requirements indicated by NS_05/NS_05U |
Ericsson, Samsung |
| R4-2504609 |
3TX chain TX switching requirements |
Qualcomm Incorporated |
| 5.3.2 |
RRM related topics |
|
| R4-2504080 |
CR 38.133 on interruption of Tx switching for 3Tx UEs [3TxSwitching] |
MediaTek inc. |
| 6.1 |
Moderator summary and conclusions (for Agenda 6) |
|
| R4-2504642 |
Topic summary for [114bis][317] 5G_Broadcast_bands |
Moderator (EBU) |
| R4-2504660 |
Topic summary for [114bis][102] NR_Baskets_Part_1 |
Moderator(Nokia) |
| R4-2504661 |
Topic summary for [114bis][103] NR_Baskets_Part_2 |
Moderator(Ericsson) |
| R4-2504662 |
Topic summary for [114bis][104] LTE_Baskets |
Moderator(Huawei) |
| R4-2504663 |
Topic summary for [114bis][105] HPUE_NR_bands |
Moderator(CMCC) |
| R4-2504664 |
Topic summary for [114bis][106] LTE_NR_HPUE_FWVM |
Moderator(Nokia) |
| R4-2504665 |
Topic summary for [114bis][107] HPUE_Basket_EN-DC |
Moderator(China Unicom) |
| R4-2504666 |
Topic summary for [114bis][108] HPUE_Basket_CADC_SUL |
Moderator(China Telecom) |
| R4-2504667 |
Topic summary for [114bis][109] LTE_NR_Other_basket |
Moderator(Huawei) |
| R4-2504668 |
Topic summary for [114bis][110] NR_IoT_NTN_Bands |
Moderator(Aalyria) |
| R4-2504669 |
Topic summary for [114bis][111] NR_mmWave_protect |
Moderator(China Unicom) |
| R4-2505093 |
WF on simultaneous Rx-Tx issues for UL CA_n5-n8 and others |
Huawei |
| R4-2505094 |
WF on n48 50MHz CBW |
Cablelab, Apple, Qualcomm |
| R4-2505095 |
WF on NR-NTN and IoT-NTN bands |
Apple |
| R4-2505117 |
WF on high power UE for NR bands |
CMCC |
| R4-2505123 |
LS on simultaneous Tx-Rx capability for TDD-SDL and TDD-FDD combinations |
Huawei |
| R4-2505214 |
WF on handling optional channel bandwidth across releases |
Skyworks |
| R4-2505215 |
WF on intra-band EN-DC configurations |
Skyworks, Apple |
| R4-2505216 |
WF for uplink CA n28-n71 |
Huawei |
| R4-2505235 |
WF on NR-NTN and IoT-NTN bands |
Apple |
| 6.2.1 |
Rapporteur input (WID/TR/big CR) |
|
| R4-2503135 |
TR37.719-21-11 v0.5.0 for DC_R19_xBLTE_yBNR_3DL2UL |
LG Electronics Deutschland |
| R4-2504094 |
TR 37.719-11-11 v0.4.0 Rel-19 Dual Connectivity of EN-DC and NE-DC configurations consisting of 2 different bands downlink (DL) with 2 different bands uplink (UL) (1 LTE band and 1 NR band) |
CHTTL |
| R4-2504097 |
draft BigCR for DC_R19_xBLTE_yBNR (OBJ-1 DC_R19_1BLTE_1BNR_2DL2UL) |
CHTTL |
| R4-2504122 |
Big draftCR for DC_R19_xBLTE_yBNR (OBJ-3 DC_R19_xBLTE_yBNR_zDLqUL) |
Nokia |
| R4-2504123 |
Big draftCR for DC_R19_xBLTE_yBNR |
Nokia, CHTTL, LG Electronics, Samsung |
| 6.2.2 |
UE RF requirements for EN-DC and NE-DC of 2 DL with 2 UL (DC_R19_1BLTE_1BNR_2DL2UL) |
|
| R4-2503241 |
DC_(n)3CA MSD evaluation |
Skyworks Solutions Inc. |
| R4-2503242 |
Clarifications on valid 1UL E-UTRA configuration for EN-DC intra-band contiguous MSD |
Skyworks Solutions Inc. |
| R4-2503367 |
TP for TR 37.719-11-11 DC_(n)3 |
Samsung, KT, [Murata, Skyworks, Apple, Qualcomm] |
| R4-2503682 |
Draft CR for TS 38.101-3 to introduce DC_3C_n71A |
Huawei, HiSilicon |
| R4-2503683 |
TP for TR 37.719-11-11 on introduction of DC_28A_n71A |
Huawei, HiSilicon |
| R4-2503684 |
TP for TR 37.719-11-11 on introduction of DC_8A_n71A |
Huawei, HiSilicon |
| R4-2503724 |
DC_(n)3CA configuration and MSD |
Murata Manufacturing Co Ltd. |
| R4-2504140 |
TP to TR 37.719-11-11 addition of DC_40A_n28A |
Nokia, Telefonica |
| R4-2505191 |
TP for TR 37.719-11-11 DC_(n)3 |
Samsung, KT, [Murata, Skyworks, Apple, Qualcomm] |
| R4-2505192 |
TP for TR 37.719-11-11 on introduction of DC_28A_n71A |
Huawei, HiSilicon |
| R4-2505193 |
TP for TR 37.719-11-11 on introduction of DC_8A_n71A |
Huawei, HiSilicon |
| R4-2505194 |
TP to TR 37.719-11-11 addition of DC_40A_n28A |
Nokia, Telefonica |
| 6.2.3 |
UE RF requirements for EN-DC and NE-DC of 2 LTE and 1 NR, or of 1 LTE and 2 NR (DC_R19_xBLTE_yBNR_3DL2UL) |
|
| R4-2503155 |
draftCR to 38.101-3 to include EN-DC band combinations (DC_R19_xBLTE_yBNR_3DL2UL) |
Huawei, Hisilicon |
| R4-2503368 |
Draft CR for TS 38.101-3 to add 3-band higher order ENDC configurations |
Samsung, KT |
| R4-2503676 |
TP for TR 37.719-21-11 on introduction of DC_1A_n40A-n71A |
Huawei, HiSilicon |
| R4-2503677 |
TP for TR 37.719-21-11 on introduction of DC_3A_n40A-n71A DC_3C_n40A-n71A |
Huawei, HiSilicon |
| R4-2503678 |
TP for TR 37.719-21-11 on introduction of DC_1A_n71A-n77A |
Huawei, HiSilicon |
| R4-2503679 |
TP for TR 37.719-21-11 on introduction of DC_3A_n71A-n77A DC_3C_n71A-n77A |
Huawei, HiSilicon |
| R4-2503681 |
Draft CR for TS 38.101-3 to introduce DC_1A-3C_n71A |
Huawei, HiSilicon |
| R4-2503685 |
TP for TR 37.719-21-11 on introduction of DC_8A-28A_n71A |
Huawei, HiSilicon |
| R4-2504141 |
TP to TR 37.719-21-11 addition of DC_1A-40A_n28A |
Nokia, Telefonica |
| R4-2504142 |
TP to TR 37.719-21-11 addition of DC_20A-38A_n28A |
Nokia, Telefonica |
| R4-2504143 |
TP to TR 37.719-21-11 addition of DC_20A-40A_n28A |
Nokia, Telefonica |
| R4-2504144 |
TP to TR 37.719-21-11 addition of DC_28A-40A_n1A |
Nokia, Telefonica |
| R4-2504145 |
TP to TR 37.719-21-11 addition of DC_3A-38A_n1A |
Nokia, Telefonica |
| R4-2504146 |
TP to TR 37.719-21-11 addition of DC_3A-40A_n28A |
Nokia, Telefonica |
| R4-2504147 |
TP to TR 37.719-21-11 addition of DC_8A-28A_n1A |
Nokia, Telefonica |
| R4-2504148 |
TP to TR 37.719-21-11 addition of DC_8A-38A_n28A |
Nokia, Telefonica |
| R4-2504149 |
TP to TR 37.719-21-11 addition of DC_8A-40A_n28A |
Nokia, Telefonica |
| R4-2504419 |
TP to TR 37.719-21-11 addition of DC_8A-38A_n78A |
Nokia, Telefonica |
| R4-2504420 |
TP to TR 37.719-21-11 addition of DC_38A-40A_n1A |
Nokia, Telefonica |
| R4-2504421 |
TP to TR 37.719-21-11 addition of DC_38A-40A_n28A |
Nokia, Telefonica |
| R4-2504489 |
Draft CR on TS 38.101-3 to correct EN-DC configurations for DC_1-28_n77 and DC_8_n28-n77 |
ZTE Corporation, Sanechips |
| R4-2505195 |
draftCR to 38.101-3 to include EN-DC band combinations (DC_R19_xBLTE_yBNR_3DL2UL) |
Huawei, Hisilicon |
| R4-2505196 |
Draft CR for TS 38.101-3 to add 3-band higher order ENDC configurations |
Samsung, KT |
| R4-2505197 |
TP for TR 37.719-21-11 on introduction of DC_3A_n40A-n71A DC_3C_n40A-n71A |
Huawei, HiSilicon |
| R4-2505198 |
TP for TR 37.719-21-11 on introduction of DC_1A_n71A-n77A |
Huawei, HiSilicon |
| R4-2505199 |
TP for TR 37.719-21-11 on introduction of DC_3A_n71A-n77A DC_3C_n71A-n77A |
Huawei, HiSilicon |
| R4-2505200 |
TP for TR 37.719-21-11 on introduction of DC_8A-28A_n71A |
Huawei, HiSilicon |
| R4-2505201 |
TP to TR 37.719-21-11 addition of DC_1A-40A_n28A |
Nokia, Telefonica |
| R4-2505202 |
TP to TR 37.719-21-11 addition of DC_20A-38A_n28A |
Nokia, Telefonica |
| R4-2505203 |
TP to TR 37.719-21-11 addition of DC_20A-40A_n28A |
Nokia, Telefonica |
| R4-2505204 |
TP to TR 37.719-21-11 addition of DC_28A-40A_n1A |
Nokia, Telefonica |
| R4-2505205 |
TP to TR 37.719-21-11 addition of DC_8A-28A_n1A |
Nokia, Telefonica |
| R4-2505206 |
TP to TR 37.719-21-11 addition of DC_8A-38A_n28A |
Nokia, Telefonica |
| R4-2505207 |
TP to TR 37.719-21-11 addition of DC_8A-40A_n28A |
Nokia, Telefonica |
| R4-2505208 |
TP to TR 37.719-21-11 addition of DC_38A-40A_n1A |
Nokia, Telefonica |
| 6.2.4 |
UE RF requirements for EN-DC and NE-DC of x LTE and y NR with total z DL bands and q UL bands (DC_R19_xBLTE_yBNR_zDLqUL) |
|
| R4-2503154 |
draftCR to 38.101-3 to include EN-DC band combinations(DC_R19_xBLTE_yBNR_zDLqUL) |
Huawei, Hisilicon |
| R4-2503369 |
Draft CR for TS 38.101-3 to add 4-band 5-band higher oder ENDC configurations |
Samsung, KT |
| R4-2503680 |
Draft CR for TS 38.101-3 to introduce DC_1A-3A_n40A-n71A/DC_1A-3C_n40A-n71A/DC_1A-3A_n71A-n77A/DC_1A-3C_n71A-n77A |
Huawei, HiSilicon |
| R4-2504490 |
Draft CR on TS 38.101-3 to add missing EN-DC configurations for delta TIB and RIB |
ZTE Corporation, Sanechips |
| R4-2504491 |
Draft CR on TS 38.101-3 to introduce new BC for DC_3-20-28_n7 |
ZTE Corporation, Sanechips |
| R4-2505209 |
Draft CR for TS 38.101-3 to add 4-band 5-band higher oder ENDC configurations |
Samsung, KT |
| 6.3.1 |
Rapporteur input (WID/TR/big CR) |
|
| R4-2503674 |
Draft Big CR on Introduction of completed SUL band combinations into TS 38.101-1 |
Huawei, HiSilicon |
| R4-2503675 |
TR for 38.719-00-00 v0.2.0 |
Huawei, HiSilicon |
| R4-2503733 |
draft big CR 38.101-1 for NR_CADC_R19_2BDL_xBUL |
ZTE Corporation, Sanechips |
| R4-2503734 |
draft big CR 38.101-2 for NR_CADC_R19_2BDL_xBUL |
ZTE Corporation, Sanechips |
| R4-2503955 |
draft big CR 38.101-1 new combinations Rel-19 NR Intra-band |
Ericsson |
| R4-2503956 |
draft big CR 38.101-2 new combinations Rel-19 NR Intra-band |
Ericsson |
| R4-2503957 |
Rel-19 NR intra-band CA combinations |
Ericsson |
| R4-2503981 |
TR38.719-02-01 v0.5.0_NR_CADC_R19_2BDL_xBUL |
ZTE Corporation |
| R4-2503982 |
draft big CR for NR_CADC_SUL_R19(OBJ-2 NR_CADC_R19_2BDL_xBUL) |
ZTE Corporation |
| R4-2504269 |
draft big CR 38.101-1 for NR_CADC_SUL_R19(OBJ-4 NR_CADC_R19_yBDL_xBUL) |
Ericsson |
| R4-2504270 |
draft big CR 38.101-3 for NR_CADC_SUL_R19(OBJ-4 NR_CADC_R19_yBDL_xBUL) |
Ericsson |
| R4-2504486 |
TR 38.719-03-01 v0.5.0 on Rel-19 NR Inter-band CA DC configurations including inter band CA for 3 different bands DL with x different bands UL (x=1,2) |
ZTE Corporation |
| R4-2504487 |
Draft big CR for NR_CADC_SUL_R19 (OBJ-3 NR_CADC_R19_3BDL_xBUL) into TS 38.101-1 |
ZTE Corporation |
| R4-2504488 |
Draft big CR for NR_CADC_SUL_R19 (OBJ-3 NR_CADC_R19_3BDL_xBUL) into TS 38.101-3 |
ZTE Corporation |
| 6.3.2 |
UE RF requirements for NR intra-band CA combinations for x CC DL/y CC UL (NR_CA_R19_Intra with/without UL-MIMO) |
|
| R4-2503243 |
Further MSD clean-up for CA intra-band non-contiguous |
Skyworks Solutions Inc. |
| R4-2504520 |
On (in)valid intra-band non-contiguous UL CA configurations |
Skyworks Solutions Inc. |
| 6.3.3 |
UE RF requirements for NR inter-band CA/DC configurations including inter band CA for 2 DL with up to 2UL (NR_CADC_R19_2BDL_xBUL) |
|
| R4-2503210 |
Draft CR for TS38.101-1 to add BCS4 and 5 for CA_n77-n79 |
SoftBank Corp. |
| R4-2503220 |
Draft CR for TR 38.101-1 include CA_n20-n41 |
Huawei, HiSilicon |
| R4-2503240 |
Cross-band isolation exception cases and corrections |
Skyworks Solutions Inc. |
| R4-2503339 |
Reply LS on UE capability for FDD-FDD inter-band CA simultaneous Rx/Tx |
MediaTek Korea Inc. |
| R4-2503482 |
draft reply LS to RAN2 on UE capability for FDD-FDD inter-band CA simultaneous Rx/Tx |
CATT |
| R4-2503686 |
TP for TR 38.719-02-01 on introduction of CA_n40A-n71A |
Huawei, HiSilicon |
| R4-2503687 |
TP for TR 38.719-02-01 on introduction of CA_n28A-n71A |
Huawei, HiSilicon |
| R4-2503692 |
Discussion and replied LS on UL CA_n5-n8 |
Huawei, HiSilicon |
| R4-2503812 |
Views on RAN2 reply LS on UE capability for FDD-FDD inter-band CA simultaneous Rx-Tx |
Apple |
| R4-2503972 |
Clarification on ULCA_n41C IMD MSD test point |
ZTE Corporation, Sanechips |
| R4-2503973 |
Reply LS on UE capability for FDD-FDD inter-band CA simultaneous RxTx |
ZTE Corporation, Sanechips |
| R4-2503975 |
TP for TR38.719-02-01_CA_n40A-n41C |
ZTE Corporation, Sanechips |
| R4-2503976 |
TP for TR38.719-02-01_CA_n41C-n79A |
ZTE Corporation, CMCC |
| R4-2503977 |
draft CR to TS38.101-1_CA_n41A-n104C and CA_n41C-n104A |
ZTE Corporation, Sanechips |
| R4-2504082 |
Draft CR for TS 38.101-3 to introduce DC band combinations consist of two bands |
Huawei, HiSilicon |
| R4-2504116 |
CA_n5A-n8A capabilities |
Qualcomm France |
| R4-2504117 |
Reply LS on UE capability for FDD-FDD inter-band CA simultaneous Rx/Tx |
Qualcomm France |
| R4-2504124 |
On LS response to RAN1 on UE capability for non-simultaneous RxTx FDD-FDD inter-band CA |
Nokia |
| R4-2504133 |
TP to TR 38.719-02-01 CA_n2-n5 |
Nokia, Verizon |
| R4-2504134 |
TP to TR 38.719-02-01 CA_n2-n48 |
Nokia, Verizon |
| R4-2504135 |
TP to TR 38.719-02-01 CA_n2-n77 |
Nokia, Verizon |
| R4-2504136 |
TP to TR 38.719-02-01 CA_n5-n48 |
Nokia, Verizon |
| R4-2504137 |
TP to TR 38.719-02-01 CA_n5-n77 |
Nokia, Verizon |
| R4-2504138 |
TP to TR 38.719-02-01 CA_n48-n66 |
Nokia, Verizon |
| R4-2504139 |
TP to TR 38.719-02-01 CA_n66-n77 |
Nokia, Verizon |
| R4-2504412 |
Draft CR for TS 38.101-1 to add bandwidth combination set 4 and 5 for inter-band CA combinations (two bands) |
Samsung, Boost Mobile Network |
| R4-2504492 |
TP for TR 38.719-02-01 to correct CA_n20-n77 |
ZTE Corporation, Sanechips |
| R4-2504493 |
Draft CR on TS 38.101-1 to correct inter-band CA configurations for two bands combinations |
ZTE Corporation, Sanechips |
| R4-2504574 |
draft CR for TS38.101-1 to add new NR DL CA n78(2A)-n79A with UL n78(2A) |
NTT DOCOMO, INC. |
| R4-2504625 |
IMD range definition for inter-band MSD due to one band contiguous CA UL configuration |
Skyworks Solutions Inc. |
| R4-2505124 |
draft reply LS to RAN2 on UE capability for FDD-FDD inter-band CA simultaneous Rx/Tx |
CATT |
| R4-2505162 |
Draft CR for TS38.101-1 to add BCS4 and 5 for CA_n77-n79 |
SoftBank Corp. |
| R4-2505163 |
TP for TR 38.719-02-01 on introduction of CA_n40A-n71A |
Huawei, HiSilicon |
| R4-2505164 |
TP for TR 38.719-02-01 on introduction of CA_n28A-n71A |
Huawei, HiSilicon |
| R4-2505165 |
draft CR to TS38.101-1_CA_n41A-n104C and CA_n41C-n104A |
ZTE Corporation, Sanechips |
| R4-2505166 |
Draft CR for TS 38.101-3 to introduce DC band combinations consist of two bands |
Huawei, HiSilicon |
| R4-2505167 |
TP to TR 38.719-02-01 CA_n2-n48 |
Nokia, Verizon |
| R4-2505168 |
TP to TR 38.719-02-01 CA_n2-n77 |
Nokia, Verizon |
| R4-2505169 |
TP to TR 38.719-02-01 CA_n5-n48 |
Nokia, Verizon |
| R4-2505170 |
TP to TR 38.719-02-01 CA_n5-n77 |
Nokia, Verizon |
| R4-2505171 |
TP to TR 38.719-02-01 CA_n48-n66 |
Nokia, Verizon |
| R4-2505172 |
TP to TR 38.719-02-01 CA_n66-n77 |
Nokia, Verizon |
| R4-2505173 |
Draft CR for TS 38.101-1 to add bandwidth combination set 4 and 5 for inter-band CA combinations (two bands) |
Samsung, Boost Mobile Network |
| 6.3.4 |
UE RF requirements for NR inter-band CA/DC configurations including inter band CA for 3 DL with x UL (NR_CADC_R19_3BDL_xBUL) |
|
| R4-2503211 |
TP for TR38.719-03-01 addition of UL CA_n77(2A) to CA_n1-n3-n77 |
SoftBank Corp. |
| R4-2503212 |
TP for TR38.719-03-01 addition of CA_n3-n78-n79 |
SoftBank Corp., LG Electronics |
| R4-2503213 |
Draft CR for TS38.101-1 to add BCS4 and 5 for 3CC NRCA combinations |
SoftBank Corp. |
| R4-2503221 |
Draft CR for TS 38101-1 include BCS 4 and 5 for CA configurations of 3BDL |
Huawei, HiSilicon,MTN |
| R4-2503222 |
draft TP to TR 38.719-03-01 include CA_n3-n78-n79 |
Huawei, HiSilicon |
| R4-2503223 |
Draft CR for TS 38101-1 include BCS 4 and 5 for CA configurations of 3BDL |
Huawei, HiSilicon |
| R4-2503688 |
TP for TR 38.719-03-01 on introduction of CA_n28A-n40A-n71A |
Huawei, HiSilicon |
| R4-2503689 |
TP for TR 38.719-03-01 on introduction of CA_n28A-n71A-n77A CA_n28A-n71A-n77(2A) |
Huawei, HiSilicon |
| R4-2503690 |
TP for TR 38.719-03-01 on introduction of CA_n40A-n71A-n77A CA_n40A-n71A-n77(2A) |
Huawei, HiSilicon |
| R4-2503780 |
Draft CR for TS38.101-1 Rel-19 for adding new NRCA combinations for FR1 for 3DL |
KDDI Corporation (TTC) |
| R4-2503978 |
TP for TR38.719-03-01_3DL_2UL CA_n3A-n34A-n41A |
ZTE Corporation, Sanechips |
| R4-2503979 |
TP for TR38.719-03-01_3DL_2UL CA_n3A-n34A-n79A |
ZTE Corporation, Sanechips |
| R4-2504068 |
draft TP to TR 38.719-03-01 include CA_n8-n78-n79 |
Huawei, HiSilicon |
| R4-2504083 |
Draft CR for TS 38.101-3 to introduce DC band combinations consist of three bands |
Huawei, HiSilicon |
| R4-2504271 |
TP for 38.719-03-01 to add UL CA_n2A-n77C and CA_n5A-n77C for CA_n2-n5-n77 |
Ericsson, Verizon |
| R4-2504272 |
TP for 38.719-03-01 to add UL CA_n2A-n77C and CA_n66A-n77C for CA_n2-n66-n77 |
Ericsson, Verizon |
| R4-2504273 |
TP for 38.719-03-01 to add UL CA_n2A-n77C for CA_n2A-n48A-n77C |
Ericsson, Verizon |
| R4-2504274 |
TP for 38.719-03-01 to add UL CA_n5A-n77C and CA_n66A-n77C for CA_n5-n66-n77 |
Ericsson, Verizon |
| R4-2504275 |
TP for 38.719-03-01 to add UL CA_n5A-n77C for CA_n5-n48-n77 |
Ericsson, Verizon |
| R4-2504276 |
TP for 38.719-03-01 to add UL CA_n66A-n77C for CA_n48-n66-n77 |
Ericsson, Verizon |
| R4-2504411 |
Draft CR for TS 38.101-1 to add bandwidth combination set 4 and 5 for inter-band CA combinations (three bands) |
Samsung, Boost Mobile Network |
| R4-2504494 |
Draft CR on TS 38.101-1 to correct inter-band CA configurations for three bands combinations |
ZTE Corporation, Sanechips |
| R4-2504495 |
Draft CR on TS 38.101-3 to introduce new BC for CA_n8--n41-n258 |
ZTE Corporation, Sanechips |
| R4-2504575 |
draft CR for TS38.101-1 to add new NRCA n1A-n78(2A)-n79A and n28A-n78(2A)-n79A |
NTT DOCOMO, INC. |
| R4-2505174 |
Draft CR for TS38.101-1 to add BCS4 and 5 for 3CC NRCA combinations |
SoftBank Corp. |
| R4-2505175 |
Draft CR for TS 38101-1 include BCS 4 and 5 for CA configurations of 3BDL |
Huawei, HiSilicon,MTN |
| R4-2505176 |
draft TP to TR 38.719-03-01 include CA_n3-n78-n79 |
Huawei, HiSilicon |
| R4-2505177 |
Draft CR for TS 38101-1 include BCS 4 and 5 for CA configurations of 3BDL |
Huawei, HiSilicon |
| R4-2505178 |
TP for TR 38.719-03-01 on introduction of CA_n28A-n40A-n71A |
Huawei, HiSilicon |
| R4-2505179 |
TP for TR 38.719-03-01 on introduction of CA_n28A-n71A-n77A CA_n28A-n71A-n77(2A) |
Huawei, HiSilicon |
| R4-2505180 |
TP for TR 38.719-03-01 on introduction of CA_n40A-n71A-n77A CA_n40A-n71A-n77(2A) |
Huawei, HiSilicon |
| R4-2505181 |
Draft CR for TS38.101-1 Rel-19 for adding new NRCA combinations for FR1 for 3DL |
KDDI Corporation (TTC) |
| R4-2505182 |
draft TP to TR 38.719-03-01 include CA_n8-n78-n79 |
Huawei, HiSilicon |
| R4-2505183 |
Draft CR for TS 38.101-3 to introduce DC band combinations consist of three bands |
Huawei, HiSilicon |
| R4-2505184 |
TP for 38.719-03-01 to add UL CA_n2A-n77C and CA_n5A-n77C for CA_n2-n5-n77 |
Ericsson, Verizon |
| R4-2505185 |
TP for 38.719-03-01 to add UL CA_n5A-n77C for CA_n5-n48-n77 |
Ericsson, Verizon |
| R4-2505186 |
draft CR for TS38.101-1 to add new NRCA n1A-n78(2A)-n79A and n28A-n78(2A)-n79A |
NTT DOCOMO, INC. |
| 6.3.5 |
UE RF requirements for NR inter-band CA/DC configurations including inter band CA for y DL with x UL (NR_CADC_R19_yBDL_xBUL) |
|
| R4-2503691 |
Draft CR for TS 38.101-1 to introduce CA_n28A-n40A-n71A-n77A |
Huawei, HiSilicon |
| R4-2504084 |
Draft CR for TS 38.101-3 to introduce DC band combinations consist of more than three bands |
Huawei, HiSilicon |
| R4-2504422 |
Draft CR 38.101-1 to add new inter-band combinations of bands n1, n3, n7, n20, and n78 |
Nokia, BT plc |
| R4-2504496 |
Draft CR on TS 38.101-1 to correct inter-band CA configurations for four bands combinations |
ZTE Corporation, Sanechips |
| R4-2505187 |
Draft CR for TS 38.101-1 to introduce CA_n28A-n40A-n71A-n77A |
Huawei, HiSilicon |
| R4-2505188 |
Draft CR for TS 38.101-3 to introduce DC band combinations consist of more than three bands |
Huawei, HiSilicon |
| R4-2505189 |
Draft CR 38.101-1 to add new inter-band combinations of bands n1, n3, n7, n20, and n78 |
Nokia, BT plc |
| 6.3.6 |
UE RF requirements for SUL and CA band combinations with SULs (NR_SUL_combos_R19) |
|
| R4-2503156 |
draftCR to 38.101-1 to include SUL band combinations(NR_CADC_SUL_R19) |
Huawei, Hisilicon |
| R4-2504497 |
Draft CR on TS 38.101-1 to correct operating bands for SUL band combinations |
ZTE Corporation, Sanechips |
| R4-2505190 |
draftCR to 38.101-1 to include SUL band combinations(NR_CADC_SUL_R19) |
Huawei, Hisilicon |
| 6.4.1 |
Rapporteur input (WID/TR/big CR) |
|
| R4-2503280 |
TR 36.719-01-01 LTE-A CA for x-DL y-UL |
Huawei Technologies France |
| R4-2503281 |
draftBig CR on Introduction of completed R19 x(1<=x<=6) DL y(y<=2) UL CA band combinations to TS 36.101 |
Huawei Technologies France |
| R4-2503282 |
draftBig CR on Introduction of completed R19 x(1<=x<=6) DL y(y<=2) UL CA band combinations to TS 36.101 |
Huawei Technologies France |
| R4-2503283 |
Revised WID Rel-19 LTE-A CA for x(1<=x<=6) DL y(y<=2) |
Huawei Technologies France |
| 6.4.2 |
UE RF requirements |
|
| R4-2503284 |
draftCR on Introduction of new LTE band combinations LTE_CA_R19_xBDL_yBUL |
Huawei Technologies France |
| R4-2505211 |
draftCR on Introduction of new LTE band combinations LTE_CA_R19_xBDL_yBUL |
Huawei Technologies France |
| 6.5.1 |
Rapporteur input (WID/TR/big CR) |
|
| R4-2504095 |
TR 38.796 v0.4.0 HPUE_NR_FR1_bands_R19-FDD |
China Unicom |
| 6.5.3 |
HPUE in a single FDD band |
|
| R4-2504185 |
Specification of PC2 and NS values for n5 and n26 |
Ericsson |
| R4-2504186 |
Draft CR to 38.101-1: Introduction of requirements for PC2 operation in band n26 |
Ericsson |
| R4-2504555 |
On HPUE PC2 requirements |
Huawei, HiSilicon |
| 6.7.1 |
Rapporteur input (WID/TR/big CR) |
|
| R4-2504103 |
TR 37.898 v0.4.0 HPUE_DC_LTE_NR_R19 |
China Unicom, Ericsson |
| R4-2504106 |
Draft Big CR on Rel-19 HPUE for DC combinations of LTE band(s) and NR band(s) |
China Unicom, Ericsson |
| 6.7.2 |
UE RF requirements |
|
| R4-2503214 |
Draft CR for TS38.101-3 addition of n77(3A) to DC_1_n77, DC_3_n77 and DC_8_n77 |
SoftBank Corp. |
| R4-2503980 |
Draft CR for 38.101-3 to remove redundant DC with TxD table |
ZTE Corporation, Sanechips, T-Mobile USA, Samsung, Qualcomm |
| R4-2505118 |
Draft CR for TS38.101-3 addition of n77(3A) to DC_1_n77, DC_3_n77 and DC_8_n77 |
SoftBank Corp. |
| 6.8.1 |
Rapporteur input (WID/TR/big CR) |
|
| R4-2503259 |
Revised WID for HPUE_NR_CADC_SUL_R19 |
China Telecom, China Unicom |
| R4-2503260 |
DraftBig CR to 38.101-1 new combinations for HPUE_NR_CADC_SUL_R19 |
China Telecom, China Unicom |
| R4-2503261 |
TR 38.746 v0.4.0 HPUE_NR_CADC_SUL_R19-TDD |
China Telecom |
| R4-2504098 |
TR 38.750 v0.5.0 HPUE_NR_CADC_SUL_R19-FDD |
China Unicom |
| R4-2504099 |
draft objective BigCR for HPUE_NR_CADC_SUL_R19 |
China Unicom |
| 6.8.3 |
UE RF requirements for inter-band CA/DC with high power on TDD band(s) |
|
| R4-2503263 |
Draft CR for TS38.101-1 Rel-19 for adding new HP-NRCA combinations for for 4 DL |
SoftBank Corp. |
| R4-2503264 |
Draft CR for TS38.101-1 Rel-19 to add PC2 ULCA_n77(2A) for CA_n41A-n77(3A) |
SoftBank Corp. |
| R4-2504132 |
Draft CR 38.101-1 to add band combinations of bands n25, n41, n66, n71 and n77 with HPUE on TDD bands |
Nokia, T-Mobile USA |
| R4-2504576 |
draft CR for TS38.101-1 to add new NRCA with high power UL n78 or n79 |
NTT DOCOMO, INC. |
| R4-2504611 |
TP for TR38.746 for adding HPUE for DL CA_n25-n41-n77 with UL CA_n41-n77 |
T-Mobile USA, Nokia |
| R4-2504612 |
TP for TR38.746 for adding HPUE for DL CA_n41-n66-n77 with UL CA_n41-n77 |
T-Mobile USA, Nokia |
| R4-2504613 |
TP for TR38.746 for adding HPUE for DL_CA_n41-n71-n77 with UL CA_n41-n77 |
T-Mobile USA, Nokia |
| R4-2505115 |
Draft CR for TS38.101-1 Rel-19 for adding new HP-NRCA combinations for for 4 DL |
SoftBank Corp. |
| R4-2505116 |
Draft CR for TS38.101-1 Rel-19 to add PC2 ULCA_n77(2A) for CA_n41A-n77(3A) |
SoftBank Corp. |
| R4-2505119 |
Draft CR 38.101-1 to add band combinations of bands n25, n41, n66, n71 and n77 with HPUE on TDD bands |
Nokia, T-Mobile USA |
| R4-2505120 |
draft CR for TS38.101-1 to add new NRCA with high power UL n78 or n79 |
NTT DOCOMO, INC. |
| R4-2505121 |
TP for TR38.746 for adding HPUE for DL CA_n25-n41-n77 with UL CA_n41-n77 |
T-Mobile USA, Nokia |
| 6.8.4 |
UE RF requirements for inter-band CA/DC with high power on FDD band(s) |
|
| R4-2503370 |
TP for TR 38.750 CA_n2-n48 with PC2 FDD single UL |
Samsung, Verizon |
| R4-2503371 |
TP for TR 38.750 CA_n48-n66 with PC2 FDD single UL |
Samsung, Verizon |
| R4-2504131 |
Draft CR 38.101-1 to add band combinations of bands n25, n41, n66, n71 and n77 with UL PC2 on FDD bands |
Nokia, T-Mobile USA |
| R4-2505122 |
TP for TR 38.750 CA_n2-n48 with PC2 FDD single UL |
Samsung, Verizon |
| 6.8.5 |
UE RF requirements for inter-band CA/DC with high power on both FDD and TDD bands |
|
| R4-2504130 |
Draft CR 38.101-1 to add 4-band combinations of bands n25, n41, n66, n71 and n77 with UL mixed TDD-FDD PC2 |
Nokia, T-Mobile USA |
| 6.9.1 |
Rapporteur input (WID/TR/big CR) |
|
| R4-2503983 |
Revised WID: Additional NR bands for NR features in Rel-19 |
ZTE Corporation, Huawei |
| R4-2503984 |
TS 38.101-1 draft big CR to include 4Rx and 8Rx |
ZTE Corporation |
| R4-2503985 |
TS 38.101-1 draft big CR for NR_bands_xFeature_R19-Core |
ZTE Corporation |
| 6.10.1 |
Rapporteur input (WID/TR/big CR) |
|
| R4-2503781 |
TR 37.887 0.0.5 Rel-19 downlink interruption for NR and EN-DC band combinations at dynamic Tx Switching in Uplink |
China Telecom |
| 6.10.2 |
UE RF requirements |
|
| R4-2503782 |
TP to 37.887: DL interruption clarification for CA_n3-n5-n78 for 3 bands dynamic Tx switching |
China Telecom |
| 6.11.1 |
Rapporteur input (WID/TR/big CR) |
|
| R4-2503143 |
TR 38.793 v0.1.0 Rel-19 Requirements for simultaneous RxTx band combinations for NR CADC, NR SUL and LTENR DC |
Huawei, Hisilicon |
| 6.11.2 |
UE RF requirements |
|
| R4-2503144 |
draftCR to 38.101-1 Simultaneous Rx-Tx |
Huawei, Hisilicon |
| R4-2503145 |
Discussion on simultaneous Rx-Tx |
Huawei, Hisilicon |
| R4-2503190 |
On simultaneous RxTx for CA_n40A-n41A |
Apple |
| R4-2504126 |
On further improvements for simultaneous Rx-Tx notes |
Nokia |
| R4-2505224 |
draftCR to 38.101-1 Simultaneous Rx-Tx |
Huawei, Hisilicon |
| R4-2505226 |
draftCR to 38.101-1 Simultaneous Rx-Tx |
Huawei, Hisilicon |
| 6.12.2 |
UE RF requirements |
|
| R4-2503163 |
TP to TR 37.862: Introduction of 3MHz channel BW for n5 and n12 |
Nokia, AT&T |
| R4-2503193 |
n48: Adding channels of 50MHz and beyond |
Apple |
| R4-2503563 |
On adding n48 NS_27 A-MPR for CBW 50MHz and higher |
Qualcomm Incorporated |
| 6.13.1 |
System parameters and UE RF requirements |
|
| R4-2503176 |
Further input on UE power back-off while operating in 2000-2020 MHz UL range of the NTN band n252 |
Apple |
| R4-2503177 |
Introduction of the NTN S-band to TS 38.101-5 |
Apple |
| R4-2503440 |
Discussion on UE RF requirements for the NTN new S-band |
CATT |
| R4-2503441 |
DraftCR for TS 38.108, Introduction on system parameters for SAN supporting New S band |
CATT |
| R4-2503565 |
Views on open issues of n252/B252 UE RF requirements |
EchoStar, Boost Mobile Network |
| R4-2503566 |
DraftCR to TR 38.863 to capture agreement for n252 introduction |
EchoStar, Boost Mobile Network |
| R4-2503697 |
Discussion on the NTN S band definition |
Huawei, HiSilicon |
| R4-2503735 |
draftCR to TS38.108 Introduction of NR-NTN S-band |
ZTE Corporation, Sanechips |
| R4-2504387 |
Discussion on NR-NTN n252 UE RF requirements |
MediaTek (Hefei) Inc. |
| R4-2504544 |
A-MPR and OOB blocking for n252 |
Qualcomm Inc. |
| R4-2505125 |
Introduction of the NTN S-band to TS 38.101-5 |
Apple |
| R4-2505126 |
DraftCR to TR 38.863 to capture agreement for n252 introduction |
EchoStar, Boost Mobile Network |
| 6.13.2 |
SAN RF core requirements |
|
| R4-2503439 |
Discussion on SAN RF requirements for the NTN new S-band |
CATT |
| R4-2504623 |
Draft CR to TS 38.108: Clause 5.2 Operating bands |
THALES |
| 6.13.3 |
RRM core requirements |
|
| R4-2503800 |
Draft CR to TS 38.133 Introduction of a new NTN S-band |
ZTECorporation,Sanechips |
| 6.14.1 |
System parameters and UE RF requirements |
|
| R4-2503443 |
DraftCR for TS 36.108, Introduction on system parameter for SAN supporting New S band |
CATT |
| R4-2504391 |
Discussion on IoT-NTN B252 UE RF requirements |
MediaTek (Hefei) Inc. |
| R4-2504522 |
DraftCR to TR 36.764 to capture agreement for B252 introduction |
Boost Mobile Network |
| R4-2504545 |
UE-to-UE coexistence and OOB blocking for B252 |
Qualcomm Inc. |
| R4-2505127 |
DraftCR to TR 36.764 to capture agreement for B252 introduction |
Boost Mobile Network |
| 6.14.2 |
SAN RF core requirements |
|
| R4-2504624 |
Draft CR to TS 36.108: Clause 5.2 Operating bands |
THALES |
| 6.14.3 |
RRM core requirements |
|
| R4-2503802 |
Draft CR to TS 36.133 Introduction of a new IoT NTN S-band |
ZTECorporation,Sanechips |
| 6.15 |
Introduction of new NR NTN bands to support the Extended L-band (UL 1668-1675MHz, DL 1518-1525MHz) and the combined MSS L-band and Extended L-band ranges |
|
| R4-2503548 |
Open items on NR_IoT_NTN_Bands |
Aalyria |
| 6.15.1 |
System parameters and UE RF requirements |
|
| R4-2503178 |
Further considerations on the emission requirements for the UE operating in 1626.5-1660.5MHz and 1668-1675MHz UL frequency ranges |
Apple |
| R4-2503179 |
Introduction of the NTN L-bands to TS 38.101-5 |
Apple |
| R4-2503442 |
DraftCR for TS 38.108, Introduction on system parameter for SAN supporting combined L band |
CATT |
| R4-2503538 |
Possible approach on L-band NS value for RA protection |
Aalyria |
| R4-2503709 |
Capturing of L-band Regulatory Requirements |
ViaSat Satellite Holdings Ltd, Inmarsat |
| R4-2503736 |
draftCR to TS38.108 Introduction of NR-NTN combined L-band |
ZTE Corporation, Sanechips |
| R4-2505128 |
Introduction of the NTN L-bands to TS 38.101-5 |
Apple |
| R4-2505129 |
draftCR to TS38.108 Introduction of NR-NTN combined L-band |
ZTE Corporation, Sanechips |
| 6.15.2 |
SAN RF core requirements |
|
| R4-2504620 |
Draft CR to TS 38.108: Clause 5.2 Operating bands |
THALES |
| 6.15.3 |
RRM core requirements |
|
| R4-2503801 |
Draft CR to TS 38.133 Introduction of a new NTN L-band |
ZTECorporation,Sanechips |
| 6.16.2 |
Band and system parameters |
|
| R4-2503953 |
New bands for LTE based 5G broadcast - band definition |
Ericsson |
| R4-2504034 |
Introduction of two new separate bands for LTE based 5G terrestrial broadcast for early deployments |
EBU |
| 6.16.3 |
UE RF requirements |
|
| R4-2504044 |
CR to TS 36.101: New bands for LTE based 5G terrestrial broadcast for early deployments, Rel-19 |
EBU, BNE |
| 6.16.4 |
BS RF core requirements |
|
| R4-2504045 |
CR to TS 36.104 : New bands for LTE based 5G terrestrial broadcast for early deployments, Rel-19 |
EBU, BNE |
| R4-2504724 |
CR to TS 36.104 : New bands for LTE based 5G terrestrial broadcast for early deployments, Rel-19 |
EBU, BNE |
| 6.17.1 |
General aspects |
|
| R4-2503146 |
TR 38.749 v0.2.0 Protection of Earth Exploration Satellite Service (EESS) |
Huawei, Hisilicon |
| 6.17.2 |
UE RF requirements |
|
| R4-2503147 |
TP to 38.749: UE requirements for Rel-19 EESS |
Huawei, Hisilicon, China Southern Power Grid |
| R4-2503148 |
draft CR to 38.101-2 EESS (Rel-15) |
Huawei, Hisilicon, China Unicom, China Southern Power Grid |
| R4-2503149 |
draft CR to 38.101-2 EESS (Rel-16) |
Huawei, Hisilicon, China Unicom, China Southern Power Grid, Ericsson, NTT DOCOMO, Qualcomm, ZTE, CATT |
| R4-2503150 |
draft CR to 38.101-2 EESS (Rel-17) |
Huawei, Hisilicon, China Unicom, China Southern Power Grid, Ericsson, NTT DOCOMO, Qualcomm, ZTE, CATT |
| R4-2503151 |
draft CR to 38.101-2 EESS (Rel-18) |
Huawei, Hisilicon, China Unicom, China Southern Power Grid, Ericsson, NTT DOCOMO, Qualcomm, ZTE, CATT |
| R4-2503946 |
EESS protection - Remaining UE RF issues |
Ericsson |
| R4-2503947 |
Draft CR to TS 38101-2 - Rel-15 EESS protection - UE RF impacts |
Ericsson |
| R4-2503949 |
EESS protection - TP to TR 38749 - UE aspects |
Ericsson |
| R4-2503974 |
TP for TR38.749 UE RF requirements (Clause 8) |
ZTE Corporation, Sanechips |
| R4-2504159 |
draft CR to add new requirements for EESS protection from Rel-15 |
NTT DOCOMO, INC. |
| R4-2504160 |
draft CR to add new requirements for EESS protection from Rel-15 |
NTT DOCOMO, INC. |
| R4-2504161 |
draft CR to add new requirements for EESS protection from Rel-15 |
NTT DOCOMO, INC. |
| R4-2504162 |
draft CR to add new requirements for EESS protection from Rel-15 |
NTT DOCOMO, INC. |
| R4-2504482 |
24 GHz EESS Band Phase 2 Compliance |
Qualcomm Incorporated |
| R4-2505130 |
TP for TR38.749 UE RF requirements (Clause 8) |
ZTE Corporation, Sanechips |
| R4-2505131 |
draft CR to 38.101-2 EESS (Rel-15) |
Huawei, Hisilicon, China Unicom, China Southern Power Grid, Ericsson, NTT DOCOMO, Qualcomm, ZTE, CATT |
| 6.17.3 |
BS RF requirements and conformance testing |
|
| R4-2503164 |
TP to TR 38.749: BS RF requirements for Protection of EESS |
Nokia |
| R4-2503948 |
EESS protection - TP to TR 38749 - BS aspects |
Ericsson |
| R4-2505132 |
EESS protection - TP to TR 38749 - BS aspects |
Ericsson |
| 7.1.1.1.1 |
General aspects (incl. duty cycle solutions, MSD rules) |
|
| R4-2503153 |
Discussion on HPUE MSD |
Huawei, Hisilicon |
| R4-2503169 |
Simplification of HPUE 2UL DeltaMSD |
Skyworks Solutions Inc. |
| R4-2503196 |
On Rel-19 HPUE CA DC MSD consideration |
Apple |
| R4-2503215 |
Further discussion on HPUE MSD rules |
Murata Manufacturing Co Ltd. |
| R4-2503225 |
On 1UL/1CC HPUE MSD rules |
Nokia, Samsung |
| R4-2503238 |
On 1UL HPUE MSD simplifications |
Skyworks Solutions Inc. |
| R4-2503239 |
Unified HPUE 1UL2UL MSD simplification proposals for Rel-19 |
Skyworks Solutions Inc., Samsung |
| R4-2503361 |
Discussion on HPUE intra-band/inter-band CA/DC with 2Tx/3Tx |
MediaTek Korea Inc. |
| R4-2503362 |
Discussion on MSD simplification of HPUE CA/DC UE |
MediaTek Korea Inc. |
| R4-2503365 |
Consideration on Rel-19 and Rel-20 HPUE band combination work |
Samsung |
| R4-2503590 |
draft CR on duty cycle SAR solution for inter-band UL CA with 3Tx |
LG Electronics |
| R4-2503592 |
draft CR on duty cycle SAR solution for inter-band EN-DC with 3Tx |
LG Electronics |
| R4-2503839 |
Discussion on HPUE MSD simplification |
vivo |
| R4-2503969 |
Consideration on R19 HPUE MSD rule |
ZTE Corporation, Sanechips |
| R4-2504118 |
MSD beyond PC3 |
Qualcomm France |
| R4-2504187 |
On the duty-cycle solutions for SAR compliance |
Ericsson |
| R4-2504614 |
MSD for 3Tx UL CA combinations with 2Tx FDD + 1Tx TDD |
T-Mobile USA |
| R4-2505210 |
draft CR on duty cycle SAR solution for inter-band EN-DC with 3Tx |
LG Electronics, Vivo |
| 7.1.1.1.2 |
Intra-band contiguous and non-contiguous UL CA with PC1.5 |
|
| R4-2503197 |
On PC1.5 intra-band UL CA MPR |
Apple |
| R4-2503279 |
MPR evaluations for contiguous intra-band CA with NC allocation for PC1.5 TxDiv |
Huawei Technologies France |
| R4-2503511 |
MPR and A-MPR for intra-band contiguous and non-contiguous UL CA for PC1.5 |
Qualcomm Technologies |
| R4-2504170 |
R19 MPR for PC1.5 contig CA |
OPPO |
| R4-2504171 |
R19 MPR for PC1.5 NCCA |
OPPO |
| R4-2504188 |
Applicability of MPR for contiguous and non-contiguous intra-band UL CA with PC1.5 |
Ericsson |
| R4-2504241 |
HPUE MPR for intra-band UL CA |
LG Electronics Finland |
| R4-2504258 |
Draft CR on -30dBm and -13dBm MPR for PC1.5 NCCA |
LG Electronics Finland |
| R4-2504282 |
draft CR on MPR for PC1.5 intra-band contiguous CA |
LG Electronics Finland |
| R4-2504294 |
draft CR on Pcmax,c for PC1.5 intra-band NC CA |
LG Electronics Finland |
| R4-2504386 |
Results for PC1.5 contiguous ULCA with comparison to PC2 and 6dB PSD imbalance |
Skyworks Solutions Inc. |
| 7.1.1.1.3 |
Inter-band UL NR-CA/EN-DC with 2 bands and 2Tx and/or 3Tx |
|
| R4-2503174 |
dCR to 38.101-1, to remove redundancies in 2Tx/3Tx notes |
Qualcomm, Nokia, Verizon, T-Mobile |
| R4-2503249 |
Discussion on HPUE inter-band UL CA and EN-DC |
SK Telecom |
| R4-2503970 |
Draft CR to TS 38.307 Release independence for R19 3Tx band combination |
ZTE Corporation, Sanechips |
| R4-2504127 |
On future HPUE Basket Arrangement |
Nokia |
| R4-2505141 |
Draft CR to TS 38.307 Release independence for R19 3Tx band combination |
ZTE Corporation, Sanechips |
| 7.1.1.1.4 |
Increasing UE transmission high power limit |
|
| R4-2503968 |
Draft Rel-19 CR for 38.101-3 on increasing higher power limit for EN-DC with 2Tx/3Tx |
ZTE Corporation, Samsung, CHTTL |
| R4-2505142 |
Draft Rel-19 CR for 38.101-3 on increasing higher power limit for EN-DC with 2Tx/3Tx |
ZTE Corporation, Samsung, CHTTL |
| 7.1.1.2.1 |
Power domain enhancements for single carrier |
|
| R4-2503189 |
On Rel-19 power domain enhancement for FR1 |
Apple |
| R4-2503224 |
On single carrier MPR Enhancement |
Nokia |
| R4-2503237 |
Flexible RB extension for improved MPR when NW BW is larger than UE CBW |
Skyworks Solutions Inc. |
| R4-2503492 |
Further discussion on power domain enhancements for single carrier |
CATT |
| R4-2503512 |
Power boosting and MPR reduction |
Qualcomm Technologies |
| R4-2503737 |
Discussion on power domain enhancements for single carrier |
ZTE Corporation |
| R4-2503837 |
Discussion on UE RF power enhancement for NR single carrier |
vivo |
| R4-2503838 |
draftCR to TS 38.101-1 on MPR reduction for single carrier |
vivo |
| R4-2503938 |
Views on Power domain enhancements for single carrier |
China Telecom |
| R4-2504062 |
Further Views on MPR Reduction |
Sony |
| R4-2504085 |
On power domain enhancements for single carrier |
Huawei, HiSilicon |
| R4-2504086 |
Draft CR for TS 38.101-1 to introduce MPR reduction for single carrier |
Huawei, HiSilicon |
| R4-2504152 |
Discussion on MPR reduction for single carrier |
OPPO |
| R4-2504189 |
Power domain enhancement for UE-specific CHBWs within a single carrier |
Ericsson |
| R4-2504240 |
Discussion on power domain enhancement for NR single carrier |
MediaTek (Wuhan) Inc. |
| R4-2504262 |
Power domain enhancements for single carrier |
Beijing Xiaomi Mobile Software |
| R4-2504373 |
Discussion on Power domain enhancements for single carrier |
LG Electronics UK |
| R4-2504512 |
Discussion on Power domain enhancements for single carrier |
LG Electronics UK |
| R4-2504543 |
Handling A-MPR with Bandwidth Extension |
Lenovo |
| 7.1.1.2.2 |
MPR applicability for FR1 intra-band UL CA |
|
| R4-2503493 |
Further discussion on MPR applicability for FR1 intra-band UL CA |
CATT |
| R4-2503738 |
DraftCR to 38.101-1 MPR applicability for FR1 intra-band contiguous UL CA |
ZTE Corporation, Sanechips |
| R4-2504560 |
Bandwidth Extension for Intra-Band UL CA with a Single CC |
Lenvovo |
| R4-2504564 |
Bandwidth Extension for Intra-Band UL CA with a Single CC |
Lenovo |
| R4-2505212 |
DraftCR to 38.101-1 MPR applicability for FR1 intra-band contiguous UL CA |
ZTE Corporation, Sanechips, Skyworks, Samsung, Huawei, Vivo |
| 7.1.1.2.3 |
MPR applicability for FR2 |
|
| R4-2503647 |
LS on introduction of new UE capabilities for FR2 MPR improvement |
Samsung |
| R4-2503992 |
draft CR to TS 38.101-2 for FR2 MPR improvements |
NTT DOCOMO, INC. |
| R4-2505144 |
LS on introduction of new UE capabilities for FR2 MPR improvement |
Samsung, Qualcomm |
| R4-2505145 |
draft CR to TS 38.101-2 for FR2 MPR improvements |
NTT DOCOMO, INC. |
| 7.1.1.3.1 |
Reference sensitivity requirements |
|
| R4-2503965 |
On release independent for 6Rx RF requirement |
ZTE Corporation, Sanechips |
| R4-2503966 |
Draft CR to TS38.101-1: Introduction of ?TRxSRS requirements for 6Rx |
ZTE Corporation, Sanechips |
| R4-2504087 |
Draft CR for TS 38.101-1 to introduce 6Rx RF requirements |
Huawei, HiSilicon |
| R4-2504372 |
Discussion on the usage of the terminology “FWA form factor” and its application for 6Rx, 4Rx and 8Rx requirements |
Anritsu Limited |
| 7.1.1.3.2 |
MIMO layer evaluation for 6Rx UE |
|
| R4-2503158 |
Discussion on 6 Layer MIMO Feasibility |
Nokia |
| R4-2503207 |
Discussion on remaining issues on 6 MIMO layer evaluation for 6Rx UE |
China Telecom |
| R4-2503524 |
On Core Requirements for MIMO Layer Support for 6Rx UE |
Apple |
| R4-2503655 |
Views on MIMO layer evaluation for 6Rx UE |
Samsung |
| R4-2504035 |
Discussion on the support of MIMO layers for 6Rx UE |
Ericsson |
| R4-2504088 |
Remaining issues for MIMO layers for 6Rx |
Huawei, HiSilicon |
| R4-2504178 |
draft LS on iIntroduction of supporting 6 layers capability for FWA device |
Huawei, HiSilicon |
| R4-2504348 |
Discussion on UE capability for 6 MIMO layer support |
MediaTek inc. |
| R4-2504561 |
Discussions on signaling requirements for 6Rx devices |
QUALCOMM Europe Inc. - Spain |
| R4-2504563 |
[Draft] LS on introducing capability signaling for 6Rx devices |
QUALCOMM Europe Inc. - Spain |
| 7.1.1.3.3 |
SRS antenna switching requirements |
|
| R4-2503820 |
Further discussion on SRS antenna switching requirements for 6Rx |
vivo |
| R4-2503821 |
Draft CR to 38.101-1 on SRS antenna switching requirements for 6Rx |
vivo |
| R4-2503822 |
LS on indication of support t3r6 SRS antenna switching capability |
vivo |
| 7.1.1.3.4 |
SRS IL imbalance |
|
| R4-2503195 |
On SRS Antenna Switching IL Imbalance Solution for 6Rx |
Apple |
| R4-2503333 |
Discussion on SRS IL imbalance for 6Rx UE |
Xiaomi |
| R4-2503846 |
Discussion on SRS IL imbalance reporting |
vivo |
| R4-2503939 |
Further study on SRS IL imbalance |
China Telecom |
| R4-2503967 |
Views on 6Rx SRS antenna IL |
ZTE Corporation, Sanechips |
| R4-2503986 |
Disscussion on SRS IL imbalance for 6RX UE |
Spreadtrum,UNISOC |
| R4-2503993 |
SRS imbalance solution considerations |
Nokia |
| R4-2504089 |
On SRS IL imbalance issue |
Huawei, HiSilicon |
| R4-2504100 |
Discussion on SRS IL imbalance for 6Rx UE |
Google |
| R4-2504121 |
SRS IL imbalance indication |
Qualcomm France |
| R4-2504163 |
Views on SRS insertion loss compensation and reporting enhancements |
Intel Corporation |
| R4-2504389 |
SRS IL imbalance issue |
Samsung |
| R4-2504562 |
SRS Power Imbalance Handling |
Lenovo |
| R4-2504580 |
On the SRS IL imbalance reporting for the SRS-AS |
Ericsson |
| 7.1.2 |
RRM core and performance requirements for 6Rx |
|
| R4-2503891 |
Discussion on RLM/BFD test cases for 6Rx UE |
Huawei, HiSilicon |
| R4-2504374 |
Discussions on RRM performance requirements of Rel-19 WI on UE RF enhancements |
Ericsson |
| 7.1.3 |
UE demodulation performance requirements for 6Rx |
|
| R4-2503142 |
Discussion on demodulation and CSI requirements for 6Rx UE |
MediaTek inc. |
| R4-2503157 |
Discussion on 6 Layer MIMO performance requirements |
Nokia |
| R4-2503208 |
Discussion on UE demodulation performance requirements for 6Rx |
China Telecom |
| R4-2503248 |
Discussions on demodulation performance requirements for 6Rx devices |
QUALCOMM Europe Inc. - Spain |
| R4-2503525 |
On UE Demodulation Performance Requirements for 6Rx |
Apple |
| R4-2503656 |
Discussion on UE demodulation performance requirements for 6Rx |
Samsung |
| R4-2503999 |
Discussion on UE demodulation performance requirements for 6Rx |
ZTE Corporation, Sanechips |
| R4-2504311 |
Overview on 6Rx performance requirements |
Huawei,HiSilicon |
| R4-2504312 |
Work plan for 6Rx performance requirements |
Huawei,HiSilicon |
| R4-2504329 |
On UE demodulation and CSI reporting requirements for 6Rx |
Ericsson |
| 7.1.4 |
Moderator summary and conclusions |
|
| R4-2503611 |
Topic summary for [114bis][201] NR_ENDC_RF_Ph4 |
Moderator (Huawei) |
| R4-2504650 |
Topic summary for [114bis][325] NR_ENDC_RF_Ph4_Demod_6Rx |
Moderator (Huawei) |
| R4-2504670 |
Topic summary for [114bis][112] NR_ENDC_RF_Ph4_part1 |
Moderator(Huawei) |
| R4-2504671 |
Topic summary for [114bis][113] NR_ENDC_RF_Ph4_part2 |
Moderator(Samsung) |
| R4-2504672 |
Topic summary for [114bis][114] NR_ENDC_RF_Ph4_part3 |
Moderator(Intel) |
| R4-2504749 |
Ad-hoc meeting minutes for [114bis][325] NR_ENDC_RF_Ph4_Demod_6Rx |
Huawei |
| R4-2504750 |
Way Forward for [114bis][325] NR_ENDC_RF_Ph4_Demod_6Rx |
Huawei |
| R4-2504892 |
WF on RRM requirements for NR_ENDC_RF_Ph4 |
Huawei |
| R4-2505099 |
WF on power domain enhancements |
Huawei |
| R4-2505100 |
WF on HPUE RF requirements |
Qualcomm, Mediatek, Skyworks, LGE |
| R4-2505101 |
WF on 6Rx RF requirements and SRS IL imbalance |
Intel |
| R4-2505139 |
Ad hoc minutes on 6Rx and SRS IL |
Intel |
| R4-2505140 |
LS on DL MIMO layers capabilities for 6Rx UEs |
Intel |
| R4-2505143 |
WF on MSD simplifcation for HPUE |
Skyworks, Nokia, Murata, Samsung, Qualcomm, Huawei, MediaTek, Vivo, ZTE, Apple |
| R4-2505225 |
LS on DL MIMO layers capabilities for 6Rx UEs |
Intel |
| 7.2.1 |
UE RF requirements for intra-band non-contiguous CA |
|
| R4-2503595 |
Tx requirements for SL intra-band non-contiguous CA |
LG Electronics |
| R4-2503597 |
TP to TR 38.787 on SL intra-band NC CA A-MPR |
LG Electronics |
| R4-2504210 |
UE RF requirments for intra-band non-contiguous CA |
OPPO |
| 7.2.3 |
Moderator summary and conclusions |
|
| R4-2504673 |
Topic summary for [114bis][115] NR_SL_intraB_CA_ITS_part1 |
Moderator(OPPO) |
| R4-2504674 |
Topic summary for [114bis][116] NR_SL_intraB_CA_ITS_part2 |
Moderator(LGE) |
| R4-2505133 |
WF on sidelink CA |
OPPo, LGE |
| 7.3.1 |
UE RF requirements maintenance for inter-band NR CA/DC with 3MHz CBW |
|
| R4-2503165 |
Draft CR to TS 38.101-1 on addition of 3 MHz channel bandwidth into Annex D.1 |
Nokia |
| R4-2503481 |
CR for less than 5MHz UE RF requirements in Rel-19 |
CATT |
| 7.3.2 |
RRM core requirements maintenance |
|
| R4-2503857 |
draft CR to TS 38.133: NR channel BW less than 5MHz for FR1 |
ZTE Corporation, Sanechips |
| R4-2503893 |
draftCR on RRM requirements for less than 5MHz Ph2 |
Huawei, HiSilicon |
| R4-2503894 |
Discussion on RRM requirements for less than 5MHz Ph2 |
Huawei, HiSilicon |
| R4-2504017 |
Core maintenance draftCR on less than 5MHz RRM requirements |
Intel Corporation |
| 7.3.3 |
RRM performance requirements |
|
| R4-2503858 |
Discussion on performance for less than 5MHz BW |
ZTE Corporation, Sanechips |
| R4-2503859 |
draft CR to TS 38.133: test cases for NR channel BW less than 5MHz for FR1 |
ZTE Corporation, Sanechips |
| R4-2503895 |
draftCR on TC 3-2 and TC 4-1 for less than 5MHz PH2 |
Huawei, HiSilicon |
| R4-2504015 |
Discussion on Performance part of less than 5MHz RRM requirements in Rel-19 |
Intel Corporation |
| R4-2504016 |
Test cases requirements for handover with PSCell delay and deactivated PSCell measurements |
Intel Corporation |
| R4-2504458 |
Discussion on RRM performance requirement for NR Less Than 5 MHz CA/DC |
Ericsson |
| R4-2504459 |
Draft CR for Rel-19 TC on PSCell addition change delay for less than 5 MHz |
Ericsson |
| R4-2504460 |
Draft CR for Rel-19 TC on SCell Activation and Deactivation Delay Requirement with less than 5 MHz |
Ericsson |
| R4-2504469 |
draftCR to 38.133 on SA event triggered reporting with PSCell 12 PRB SSB without |
Nokia |
| R4-2504472 |
draftCR to 38.133 on SA event triggered reporting with PSCell 12 PRB SSB without DRX |
Nokia |
| R4-2504934 |
draft CR to TS 38.133: test cases for NR channel BW less than 5MHz for FR1 |
ZTE Corporation, Sanechips |
| R4-2504935 |
draftCR on TC 3-2 and TC 4-1 for less than 5MHz PH2 |
Huawei, HiSilicon |
| R4-2504936 |
Test cases requirements for handover with PSCell delay and deactivated PSCell measurements |
Intel Corporation |
| R4-2504937 |
Draft CR for Rel-19 TC on PSCell addition change delay for less than 5 MHz |
Ericsson |
| R4-2504938 |
draftCR to 38.133 on SA event triggered reporting with PSCell 12 PRB SSB without DRX |
Nokia |
| 7.3.4 |
UE demodulation performance requirements |
|
| R4-2503209 |
Discussion on UE demodulation performance requirements for NR channel bandwidth less than 5MHz |
China Telecom |
| R4-2503526 |
On UE Demodulation Performance Requirements for NR Channel BW less than 5MHz for FR1 Phase 2 |
Apple |
| R4-2503657 |
Discussion on UE demodulation performance requirements for less than 5MHz FR1 Phase 2 |
Samsung |
| R4-2503923 |
Discussion on UE CA Demodulation performance requirements for lessthan 5MHz |
Nokia |
| R4-2504313 |
On CA performance requirements for less than 5MHz |
Huawei,HiSilicon |
| R4-2504347 |
UE demodulation requirements for CA including 3MHz CBW |
Ericsson |
| 7.3.5 |
Moderator summary and conclusions |
|
| R4-2503612 |
Topic summary for [114bis][202] NR_FR1_lessthan_5MHz_BW_Ph2 |
Moderator (Intel) |
| R4-2504651 |
Topic summary for [114bis][326] NR_less_than_5MHz_Ph2_demod |
Moderator (China Telecom) |
| R4-2504675 |
Topic summary for [114bis][117] NR_FR1_5MHz_BW_Ph2 |
Moderator(Intel) |
| R4-2504705 |
Offline meeting minutes for [114bis][326] NR_less_than_5MHz_Ph2_demod |
China Telecom |
| R4-2504754 |
Way Forward for [114bis][326] NR_less_than_5MHz_Ph2_demod |
China Telecom |
| R4-2504893 |
WF on RRM requirements for NR_FR1_lessthan_5MHz_BW_Ph2 |
Intel |
| 7.4.1 |
UE RF requirements |
|
| R4-2504119 |
Intra-band Non-collocated NR CA/EN-DC requirements |
Qualcomm France |
| 7.4.1.1 |
UE RF requirements for Type 4a/4b capable FWA UE for EN-DC/NR-CA |
|
| R4-2503278 |
LS on Rel-19 signaling support for intra-band non-collocated NR-CA, EN-DC |
Huawei Technologies France |
| R4-2503364 |
LS to RAN2 on Type-4 for non-collocated deployment |
Samsung |
| R4-2504197 |
UE RF requirements for Type 4a/4b capable FWA UE for EN-DC/NR-CA |
Ericsson |
| R4-2504203 |
draft CR to introduce Rel-19 intra-band non-collocated requirement |
OPPO |
| R4-2505161 |
LS to RAN2 on Type-4 for non-collocated deployment |
Samsung |
| 7.4.1.2 |
UE Capability/UE behavior and network signaling for Type 4 EN-DC/NR-CA |
|
| R4-2503226 |
On non-collocated intra-band EN-DC and NR-CA open issues |
Nokia |
| R4-2503228 |
LS to RAN2 on Type-4 for non-collocated deployment |
Nokia |
| R4-2503277 |
Remaining discussions on UE capability for type 4 UEs |
Huawei Technologies France |
| R4-2503363 |
Discussion on UE and NW behavior for non-collocated deployment |
Samsung |
| R4-2503583 |
On signalling support for type 4 UE |
Apple |
| R4-2503714 |
Discussion on UE Capability and BS Signaling for non-collocated Type 4a4b |
KDDI Corporation |
| R4-2503971 |
Discussion on UE Capability UE behavior and network signaling for Type 4 NR CA/ENDC |
ZTE Corporation, Sanechips |
| R4-2504198 |
UE Capability/UE behavior and network signaling for Type 4 EN-DC/NR-CA |
Ericsson |
| R4-2504209 |
UE capability and network signalling for type 4 |
OPPO |
| 7.4.1.3 |
Other aspects (incl. clarification of contiguous LTE CCs) |
|
| R4-2503584 |
draft CR on scheduling availability for type 4 UE |
Apple |
| R4-2504208 |
other aspects |
OPPO |
| R4-2504966 |
draft CR on scheduling availability for type 4 UE |
Apple |
| 7.4.2 |
RRM core requirements |
|
| R4-2503506 |
draftCR on MTTD/MRTD for intra-band non-collocated scenarios Phase 2 |
Nokia, Nokia Shanghai Bell |
| R4-2503507 |
RRM requirements for intra-band non-collocated scenarios Phase2 |
Nokia, Nokia Shanghai Bell |
| R4-2503860 |
draftCR on SCell Activation Delay Requirement for NonCol_intraB |
ZTE Corporation, Sanechips |
| R4-2503881 |
Discussion on RRM requirements for supporting intra-band non-collocated EN-DC/NR-CA deployment Phase2: new receiver type(s) |
Huawei, HiSilicon |
| R4-2503882 |
Draft CR on RRM requirements for supporting intra-band non-collocated EN-DC/NR-CA deployment Phase2: new receiver type(s) |
Huawei, HiSilicon |
| R4-2504199 |
Remaining requirements for type 4 UEs in non-colocated scenario |
Ericsson |
| R4-2504200 |
DraftCR: Scheduling availability of UE during radio link monitoring |
Ericsson |
| R4-2504201 |
DraftCR: Scheduling availability of UE performing beam failure detection + L1-RSRP |
Ericsson |
| R4-2504292 |
Draft CR on interruption requirements for Type 4 EN-DCNR-CA |
Samsung |
| R4-2504942 |
draftCR on MTTD/MRTD for intra-band non-collocated scenarios Phase 2 |
Nokia, Nokia Shanghai Bell |
| R4-2504943 |
draftCR on SCell Activation Delay Requirement for NonCol_intraB |
ZTE Corporation, Sanechips |
| R4-2504944 |
Draft CR on RRM requirements for supporting intra-band non-collocated EN-DC/NR-CA deployment Phase2: new receiver type(s) |
Huawei, HiSilicon |
| R4-2504945 |
DraftCR: Scheduling availability of UE during radio link monitoring |
Ericsson |
| R4-2504946 |
DraftCR: Scheduling availability of UE performing beam failure detection + L1-RSRP |
Ericsson |
| R4-2504947 |
Draft CR on interruption requirements for Type 4 EN-DCNR-CA |
Samsung |
| 7.4.3 |
Moderator summary and conclusions |
|
| R4-2503613 |
Topic summary for [114bis][203] NonCol_intraB_ENDC_NR_CA_Ph2 |
Moderator (Huawei) |
| R4-2504676 |
Topic summary for [114bis][118] NonCol_intraB_ENDC_NR_CA |
Moderator(KDDI) |
| R4-2504894 |
WF on RRM requirements for NonCol_intraB_ENDC_NR_CA_Ph2 |
Huawei |
| R4-2505110 |
WF on UE requirements for non-collocated scenario |
KDDI |
| 7.5.1 |
General aspects |
|
| R4-2503479 |
TP to TR 38.755 on Clause 5 |
CATT |
| R4-2504105 |
draft update TR 38.755 FR1 Fragmented carriers_rm |
MediaTek Inc. |
| R4-2504129 |
General aspects of Fragmented CA |
Nokia |
| R4-2504211 |
draft update TR 38.755 FR1 Fragmented carriers |
MediaTek Inc. |
| R4-2504452 |
TP on UE RF requirements impact for fragmented carriers |
Apple |
| R4-2504453 |
Draft LS on signaling aspects for fragmented carriers |
Apple |
| R4-2505158 |
draft update TR 38.755 FR1 Fragmented carriers_rm |
MediaTek Inc. |
| 7.5.2 |
Methods for reducing the number of UE Rx chains |
|
| R4-2503337 |
Methods for reducing the number of UE Rx chains |
Xiaomi |
| R4-2503366 |
On fallback behavior and signalling aspect for Fragmented carriers |
Samsung |
| R4-2503556 |
Procedures for fragmented carriers |
Qualcomm Incorporated |
| R4-2503835 |
Discussion on methods for reducing the number of UE RX chains |
vivo |
| R4-2503963 |
Discussion the methods for reducing the number of UE Rx chain |
ZTE Corporation, Sanechips |
| R4-2504036 |
Discussion on UE capability indication for single Rx chain |
Ericsson |
| R4-2504102 |
Discussion on methods for reducing the number of UE Rx chains for fragmented carriers |
Google |
| R4-2504153 |
Discussion on reducing the number of UE Rx chains |
OPPO |
| R4-2504173 |
Discussion on methods for reducing the number of UE Rx chains |
Nokia |
| R4-2504179 |
Discussion on methods for reducing the number of UE RX chains |
Spreadtrum,UNISOC |
| R4-2504213 |
Discussion on one Rx RF chain mode signalling aspects |
MediaTek Inc. |
| R4-2504260 |
Views on the usage of the FR1 fragmented carriers |
CHTTL |
| R4-2504283 |
On signalling aspect of fragmented carriers |
Huawei, HiSilicon |
| R4-2504450 |
On methods for reducing the number of UE Rx chains for fragmented carriers |
Apple |
| 7.5.3 |
Impacts on UE RF requirements and DL performance |
|
| R4-2503338 |
Impacts on UE RF requirements and DL performance |
Xiaomi |
| R4-2503557 |
UE performance in one RX mode |
Qualcomm Incorporated |
| R4-2503558 |
TP for TR38.755: Company C evaluation results |
Qualcomm Incorporated |
| R4-2503836 |
Impacts on UE RF requirements and DL performance |
vivo |
| R4-2503964 |
Discussion on the RF requirement for fragmented carrier |
ZTE Corporation, Sanechips |
| R4-2504037 |
Discussion on the DL PCell REFSENS degradation of fragmented carriers |
Ericsson |
| R4-2504128 |
Discussion on RF requirements for Fragmented CA |
Nokia |
| R4-2504154 |
Discussion on impacts on UE RF requirements |
OPPO |
| R4-2504214 |
Discussion of impacts on UE RF requirements and DL performance |
MediaTek Inc. |
| R4-2504239 |
Discussion of impacts on UE RF requirements and DL performance |
Spreadtrum,UNISOC |
| R4-2504284 |
On RF requirements of fragmented carriers |
Huawei, HiSilicon |
| R4-2504426 |
Link budget calculation results for fragmented carrier |
Samsung |
| R4-2504451 |
On UE RF requirements for fragmented carriers |
Apple |
| R4-2505159 |
Discussion of impacts on UE RF requirements and DL performance |
Spreadtrum,UNISOC |
| 7.5.4 |
Moderator summary and conclusions |
|
| R4-2504677 |
Topic summary for [114bis][119] FS_NR_DL_Frag_Carrier |
Moderator(Mediatek) |
| R4-2505109 |
WF on fragemented DL |
MediaTek, Apple, Qualcomm |
| R4-2505157 |
Ad hoc minutes on fragmented DL |
MediaTek |
| 7.6.1 |
UE RF requirements |
|
| R4-2503198 |
On PC2 RedCap n1 and n3 1Rx REFSENS |
Apple |
| R4-2503318 |
Discussion on PC2 RedCap RSD |
Xiaomi |
| R4-2503457 |
Discussion on UE RF requirements for RedCap PC2 FDD |
CATT |
| R4-2503458 |
Draft CR for 38.101-1: Introduction onpower class 2 RedCap for TDD bands and FDD bands |
CATT |
| R4-2503696 |
Discussion on the Rel-19 PC2 FDD RedCap UE |
Huawei, HiSilicon |
| R4-2503783 |
RF Rx requirements for PC2 RedCap in FDD bands |
China Telecom |
| R4-2503784 |
Draft CR for 38.101-1 to introduce PC2 RedCap |
China Telecom |
| R4-2503961 |
On PC2 RedCap in FR1 |
ZTE Corporation, Sanechips |
| R4-2504120 |
RedCap PC2 FDD REFSENS |
Qualcomm France |
| R4-2504402 |
RF Impact for FDD bands for PC2 RedCap |
Ericsson |
| 7.6.2 |
Moderator summary and conclusions |
|
| R4-2504678 |
Topic summary for [114bis][120] NR_PC2_RedCap_UE |
Moderator(China Telecom) |
| R4-2505102 |
WF on PC2 RedCap UE RF requirements |
China Telecom |
| R4-2505231 |
WF on PC2 RedCap UE RF requirements |
China Telecom |
| 7.7.1 |
General aspects |
|
| R4-2503477 |
TP to TR 38.768 on switching periods |
CATT |
| R4-2503550 |
TP to TR38.768 on operator provided scenarios for low band aggregation via switching |
Apple |
| R4-2505146 |
TR38.768 for low band aggregation via switching |
Apple |
| R4-2505147 |
TP to TR38.768 on operator provided scenarios for low band aggregation via switching |
Apple |
| 7.7.2 |
UE RF requirements and UE capability |
|
| R4-2503152 |
Discussion on LB-LB switching |
Huawei, Hisilicon |
| R4-2503194 |
UE RF requirements for LB CA via switching |
Apple |
| R4-2503244 |
PA transients for LB-LB switching |
Skyworks Solutions Inc. |
| R4-2503336 |
LB (FDD) – LB (SDL) CA with switching |
Xiaomi |
| R4-2503478 |
On UE RF requirements and UE capability for low band CA via switching |
CATT |
| R4-2503561 |
RX Switching time, frequency and location |
Qualcomm Incorporated |
| R4-2503599 |
Discussion on UE RF requirements of LB carrier aggregation |
LG Electronics |
| R4-2503731 |
Discussion on UE RF requirements for LB-LB CA switching |
Spreadtrum,UNISOC |
| R4-2503845 |
Discussion of UE RF impact for LB-LB switching |
vivo |
| R4-2503962 |
View on low-low band CA via switching |
ZTE Corporation, Sanechips |
| R4-2503994 |
NR_LBCA_Sw Considerations |
Nokia |
| R4-2504101 |
Discussion on low-band CA switching |
MediaTek Inc. |
| R4-2504104 |
Discussion on low band carrier aggregation via switching |
Google |
| R4-2504190 |
RF requirements for low-band CA via switching |
Ericsson |
| R4-2504388 |
UE RF requirements for LB CA via switching |
Samsung |
| 7.7.3 |
RRM core requirements |
|
| R4-2503256 |
RRM requirements for low band carrier aggregation via switching |
Qualcomm Incorporated |
| R4-2503329 |
Discussion on LB-CA RRM requirements |
Xiaomi |
| R4-2503359 |
Discussion on RRM requirements for low band carrier aggregation via switching |
OPPO |
| R4-2503421 |
Discussion on the impacts of low band CA via switching on RRM requirements |
CATT |
| R4-2503532 |
On RRM requirement for R19 LB CA |
Apple |
| R4-2503702 |
Discussion on RRM requirements for Low Band CA operation |
LG Electronics Inc. |
| R4-2503890 |
Discussion on low band carrier aggregation via switching |
Huawei, HiSilicon |
| R4-2503933 |
Discussion on RRM core requirements for LB CA via switching |
Ericsson |
| R4-2504028 |
Further discussion on RRM requirements for LB CA via switching |
vivo |
| R4-2504253 |
Discussion on RRM aspects of R19 Low band carrier aggregation via switching |
ZTE Corporation, Sanechips |
| R4-2504285 |
General discussion on RRM requirements for LB CA switching |
Samsung |
| R4-2504478 |
Discussion on low-band CA switching |
MediaTek inc. |
| R4-2504499 |
On LBCA RRM requirement impact |
Nokia |
| 7.7.4 |
Moderator summary and conclusions |
|
| R4-2503614 |
Topic summary for [114bis][204] NR_LBCA_Sw |
Moderator (Apple) |
| R4-2504679 |
Topic summary for [114bis][121] NR_LBCA_Sw |
Moderator(Apple) |
| R4-2504895 |
WF on RRM requirements for NR_LBCA_Sw |
Apple |
| R4-2504956 |
LS of RAN4 RRM agreements on LB CA via switching |
Apple |
| R4-2504969 |
LS of RAN4 RRM agreements on LB CA via switching |
Apple |
| R4-2505103 |
WF on UE RF requirements for LB CA via switching |
Apple |
| R4-2505223 |
WF on UE RF requirements for LB CA via switching |
Apple |
| 7.8.1 |
General aspects |
|
| R4-2503473 |
Clarification on the usage of 7MHz channel bandwidth |
CATT |
| R4-2503476 |
draftCR to TS 38.115-1 on 7MHz channel bandwidth |
CATT |
| 7.8.2 |
UE RF requirements and system parameters |
|
| R4-2503192 |
On the introduction of 7MHz CBW |
Apple |
| R4-2503232 |
n26 7 MHz A-MPR simulations and proposal |
Nokia |
| R4-2503262 |
Discussion on initial BWP size restriction to 5 MHz for 7MHz Channel Bandwidth |
China Telecom |
| R4-2503276 |
draftCR for Tx RF requirements for introduction of 7MHz |
Huawei Technologies France |
| R4-2503474 |
Further discussion on UE RF requirements for 7MHz channel bandwidth |
CATT |
| R4-2503642 |
Discussion on A-MPR of 7MHz for band n26 |
ZTE Corporation, Sanechips |
| R4-2503950 |
7 MHz channel BW: UE RF and system parameters |
Ericsson |
| R4-2504261 |
Discussion on UE RF requirements for 7MHz CBW |
MediaTek (Wuhan) Inc. |
| R4-2504475 |
draft CR to 38.101-1: Introduction of 7 MHz channel bandwidth for n26 and n5 |
Nokia |
| R4-2504484 |
Band n26 A-MPR Analysis for 7 MHz Channel Bandwidth |
Qualcomm Incorporated |
| R4-2504485 |
7 MHz Channel Bandwidth for n5 and n26 |
Qualcomm Incorporated |
| R4-2505134 |
7 MHz Channel Bandwidth for n5 and n26 |
Qualcomm Incorporated |
| R4-2505135 |
draftCR for Tx RF requirements for introduction of 7MHz |
Huawei Technologies France |
| R4-2505136 |
Introduction of 7 MHz channel bandwidth for n26 and n5 |
Nokia |
| 7.8.3 |
BS RF core requirements |
|
| R4-2503234 |
On BS specification impact due to introduction of 7MHz channel bandwidth |
Nokia |
| R4-2503475 |
Further discussion on BS RF requirements for 7MHz channel bandwidth |
CATT |
| R4-2503643 |
Discussion on BS RF requirements for supporting 7 MHz channel bandwidth |
ZTE Corporation, Sanechips |
| R4-2503644 |
Draft CR to TS37.104: Introduction of 7 MHz NR FR1 channel bandwidth |
ZTE Corporation, Sanechips |
| R4-2503951 |
7 MHz channel BW: BS RF impacts |
Ericsson |
| R4-2503952 |
Draft running CR to TS 38.104 - Introduction of 7 MHz channel BW |
Ericsson |
| R4-2504588 |
OTA requirements consideration for network-nodes specifications for 7MHz channel introduction |
Huawei, HiSilicon |
| R4-2504589 |
Draft CR to TS 37.105: 7MHz channel bandwidth introduction |
Huawei, HiSilicon |
| R4-2504590 |
Draft CR to TS 37.145-1: 7MHz channel bandwidth introduction |
Huawei, HiSilicon |
| R4-2504591 |
Draft CR to TS 37.145-2: 7MHz channel bandwidth introduction |
Huawei, HiSilicon |
| R4-2504592 |
Draft CR to TS 38.141-2: 7MHz channel bandwidth introduction |
Huawei, HiSilicon |
| R4-2504593 |
Draft CR to TS 38.176-2: restriction of 7MHz channel bandwidth introduction |
Huawei, HiSilicon |
| R4-2505137 |
Draft CR to TS37.104: Introduction of 7 MHz NR FR1 channel bandwidth |
ZTE Corporation, Sanechips |
| R4-2505138 |
Draft running CR to TS 38.104 - Introduction of 7 MHz channel BW |
Ericsson |
| R4-2505233 |
Draft CR to TS 37.105: 7MHz channel bandwidth introduction |
Huawei, HiSilicon |
| 7.8.4 |
Moderator summary and conclusions |
|
| R4-2504680 |
Topic summary for [114bis][122] NR_FR1_7MHz_BW |
Moderator(Ericsson) |
| R4-2505098 |
WF on UE and BS RF requirements for 7MHz channel bandwidth |
Ericsson |
| 7.9.1 |
General aspects and work plan |
|
| R4-2504070 |
Work plan for WID: New LTE band for 5G broadcast for region 3 utilizing a geosynchronous satellite |
ASTRUM MOBILE PTE. LTD. |
| 7.9.2 |
Band definition and system parameters |
|
| R4-2503747 |
Discussions on band definition and system parameters for supporting new SDO band for LTE-based 5G Broadcast |
ZTE Corporation, Sanechips |
| R4-2504053 |
Discussion on band definition and system parameters |
Qualcomm Incorporated, Astrum Mobile |
| 7.9.3 |
UE RF core requirements |
|
| R4-2503549 |
On Rx requirements for new satellite broadcast band |
Apple |
| R4-2503748 |
Discussion on UE RF requirements for supporting new SDO band for LTE-based 5G Broadcast |
ZTE Corporation, Sanechips |
| R4-2504054 |
Discussion on UE RF requirements |
Qualcomm Incorporated |
| 7.9.4 |
SAN RF core requirements |
|
| R4-2503749 |
Discussion on SAN RF requirements for supporting new SDO band for LTE-based 5G Broadcast |
ZTE Corporation, Sanechips |
| R4-2504093 |
Discussion on SAN RF requirements |
ASTRUM MOBILE PTE. LTD. |
| 7.9.5 |
Moderator summary and conclusions |
|
| R4-2504643 |
Topic summary for [114bis][318] 5G_Broadcast_GSO_NTN_band |
Moderator (Astrum) |
| R4-2504725 |
Way Forward for [114bis][318] 5G_Broadcast_GSO_NTN_band |
Astrum, Qualcomm, ZTE |
| 7.10.1 |
General aspects |
|
| R4-2504330 |
Potential impacts on spec and TR from HPUE |
Samsung |
| 7.10.2 |
UE RF requirements for NTN HPUE |
|
| R4-2503708 |
On NR-NTN HPUE requirements |
ViaSat Satellite Holdings Ltd, Inmarsat |
| 7.10.2.1 |
Coexistence study for example bands |
|
| R4-2503319 |
NTN and IoT-NTN HPUE co-existence study and calibration |
xiaomi |
| R4-2504331 |
Simulation assumption for co-existence study |
Samsung |
| R4-2504332 |
Summary of NTN HPUE co-existence study |
Samsung |
| 7.10.2.2.1 |
Tx requirements |
|
| R4-2503180 |
Further considerations on the high-power UE Tx requirements |
Apple |
| R4-2503181 |
Initial power back-off results for PC2 on NTN L-/S-band |
Apple, Globalstar |
| R4-2503182 |
Initial power back-off results for PC2 on NTN S-band |
Apple |
| R4-2503183 |
On restricted set of power back-off simulations for the satellite band UE Tx requirements |
Apple |
| R4-2503448 |
Discussion on UE Tx requirement for NTN support HPUE |
CATT |
| R4-2503699 |
Discussion on Tx requirements for NR NTN HPUE |
Huawei, HiSilicon |
| R4-2503719 |
Discussion for UE RF Tx requirements of NTN_NR_HPUE |
LG Electronics France |
| R4-2503840 |
NR NTN HPUE Tx Requirements and feasibility analysis |
vivo |
| R4-2504155 |
Discussion on Tx requirements for NR-NTN HPUE |
OPPO |
| R4-2504333 |
On NR-NTN HPUE Tx requirements |
Samsung |
| R4-2504376 |
Discussion on NR-NTN HPUE TX RF requirements |
MediaTek (Hefei) Inc. |
| R4-2504546 |
NR NTN HPUE Tx requirements |
Qualcomm Inc. |
| R4-2504584 |
On the UE RF Tx requirements for NR-NTN HPUE |
Ericsson |
| R4-2504610 |
Initial power boosting result for NR-NTN for a PC2 NR PA |
Skyworks Solutions Inc. |
| 7.10.2.2.2 |
Rx requirements |
|
| R4-2503322 |
RF requirements for NR-NTN |
xiaomi |
| R4-2503449 |
Discussion on UE Rx requirement for NTN support HPUE |
CATT |
| R4-2503700 |
Discussion on Rx requirements for NR NTN HPUE |
Huawei, HiSilicon |
| R4-2503722 |
Discussion for UE RF Rx requirements of NTN_NR_HPUE |
LG Electronics |
| R4-2503841 |
NR NTN HPUE Rx Requirements |
vivo |
| R4-2504156 |
Discussion on Rx requirements for NR-NTN HPUE |
OPPO |
| R4-2504334 |
On NR-NTN HPUE Rx requirements |
Samsung |
| R4-2504379 |
Discussion on NR-NTN HPUE RX RSD |
MediaTek (Hefei) Inc. |
| R4-2504547 |
NR NTN HPUE Rx requirements |
Qualcomm Inc. |
| R4-2504585 |
On the UE RF Rx requirements for NR-NTN HPUE |
Ericsson |
| 7.10.2.3.1 |
Tx requirements |
|
| R4-2503321 |
RF requirements for IoT-NTN |
xiaomi |
| R4-2503842 |
Iot NTN HPUE Tx Requirements and feasibility analysis |
vivo, SmarterMicro |
| R4-2504157 |
Discussion on Tx requirements for IoT-NTN HPUE |
OPPO |
| R4-2504172 |
R19 on NTN SAR |
OPPO |
| R4-2504335 |
On IoT-NTN HPUE Tx requirements and handheld SAR |
Samsung |
| R4-2504378 |
Discussion on IoT-NTN HPUE TX RF requirements |
MediaTek (Hefei) Inc. |
| R4-2504548 |
IoT NTN HPUE Tx requirements |
Qualcomm Inc. |
| R4-2504586 |
On the UE RF Tx requirements for IoT-NTN HPUE |
Ericsson, Sony, Nokia |
| R4-2504604 |
Initial power boosting result for NB-IoT-NTN for a PC2 NR PA |
Skyworks Solutions Inc. |
| 7.10.2.3.2 |
Rx requirements |
|
| R4-2503843 |
Iot NTN HPUE Rx Requirements |
vivo |
| R4-2504158 |
Discussion on Rx requirements for IoT-NTN HPUE |
OPPO |
| R4-2504336 |
On IoT-NTN HPUE Rx requirements |
Samsung |
| R4-2504385 |
Discussion on IoT-NTN HPUE RX RSD |
MediaTek (Hefei) Inc. |
| R4-2504549 |
IoT NTN HPUE Rx requirements |
Qualcomm Inc. |
| R4-2504587 |
On the UE RF Rx requirements for IoT-NTN HPUE |
Ericsson |
| 7.10.3.1 |
System parameters |
|
| R4-2503446 |
Discussion on system parameter for NTN support spectrum less than 5 MHz |
CATT |
| R4-2503739 |
LS on UE capability signalling for NTN less than 5MHz |
ZTE Corporation, Sanechips |
| R4-2504582 |
On system parameters for less than 5 MHz CBW for NTN |
Ericsson |
| R4-2504712 |
LS on UE capability signalling for NTN less than 5MHz |
ZTE Corporation, Sanechips, Xiaomi |
| 7.10.3.2 |
UE RF requirements |
|
| R4-2503184 |
Power back-off values for the 3MHz channel in band n254 |
Apple, Globalstar |
| R4-2503185 |
Power back-off values for the 3MHz channel in band n256 |
Apple |
| R4-2503186 |
Addition of the 3MHz channel to TS 38.101-5 (sub-clause 6.2) |
Apple |
| R4-2503187 |
Addition of the 3MHz channel to TR 38.863 |
Apple, Thales, Echostar, Aalyria Technologies |
| R4-2503188 |
Addition of the 3MHz channel to TR 38.741 |
Apple, Globalstar |
| R4-2503265 |
draftCR for RF requirements for introduction of 3MHz on NTN bands |
Huawei Technologies France |
| R4-2503266 |
REFSENS for NTN bands supporting 3MHz CBW |
Huawei Technologies France |
| R4-2503330 |
Discussion on UE RF requirements for NTN less than 5MHz |
Xiaomi |
| R4-2503331 |
Draft big CR on UE RF requirements for NTN less than 5MHz |
Xiaomi |
| R4-2503447 |
Discussion on UE RF requirements for NTN support spectrum less than 5 MHz |
CATT |
| R4-2504259 |
NTN n254 3 MHz A-MPR proposal + other CBWs |
Nokia |
| R4-2504337 |
On NTN Less than 5MHz UE RF requirements |
Samsung |
| R4-2504410 |
Discussion on NR-NTN 3MHz REFSENS requirements |
MediaTek (Hefei) Inc. |
| R4-2504554 |
UE RF requirements for NTN less than 5 MHz |
Qualcomm Inc. |
| R4-2504583 |
On the UE RF requirements for less than 5 MHz CBW for NTN |
Ericsson |
| R4-2504709 |
Addition of the 3MHz channel to TS 38.101-5 (sub-clause 6.2) |
Apple |
| R4-2504710 |
Addition of the 3MHz channel to TR 38.863 |
Apple, Thales, Echostar, Aalyria Technologies |
| R4-2504711 |
Addition of the 3MHz channel to TR 38.741 |
Apple, Globalstar |
| 7.10.3.3 |
SAN RF core and conformance requirements |
|
| R4-2503166 |
Draft big CR to TS 38.181 to introduce less than 5MHz for NTN |
Nokia, ZTE Corporation, Sanechips, CATT, Samsung |
| R4-2503201 |
Draft CR to TS 38.181 for section 4 and 6 |
Samsung |
| R4-2504714 |
Draft big CR to TS 38.181 to introduce less than 5MHz for NTN |
Nokia, ZTE Corporation, Sanechips, CATT, Samsung |
| 7.10.3.4 |
RRM core requirements |
|
| R4-2503323 |
Discussion on RRM requirements for less than 5MHz NTN |
Xiaomi |
| R4-2503325 |
draftCR on NTN less than 5MHz (9.2C NR intra-frequency measurements for SAN) |
Xiaomi |
| R4-2503326 |
Draft big CR on RRM requirements for NTN less than 5MHz in Rel-19 |
Xiaomi |
| R4-2503423 |
Further discussion on less than 5MHz for NTN RRM requirement |
CATT |
| R4-2503537 |
On less than 5MHz for NTN RRM |
Apple |
| R4-2503662 |
Discussion on RRM core requirements of Rel-19 NR-NTN in less than 5MHz |
Samsung |
| R4-2503664 |
Draft CR on NR SAN FR1 conditional handover for NTN less than 5MHz |
Samsung |
| R4-2503795 |
Discussion on RRM requirements for less than 5M in NTN |
ZTECorporation,Sanechips |
| R4-2503896 |
Discussion on RRM requirements for less than 5MHz for NTN |
Huawei, HiSilicon |
| R4-2503897 |
draftCR on requirments for less than 5MHz for NTN |
Huawei, HiSilicon |
| R4-2504109 |
Discussion on RRM requirements of NTN with channel BW less than 5MHz |
Ericsson |
| R4-2504445 |
SSB index detection requirements in Less than 5 MHz operation in NTN. |
Nokia |
| R4-2504951 |
draftCR on NTN less than 5MHz (9.2C NR intra-frequency measurements for SAN) |
Xiaomi |
| R4-2504952 |
Draft CR on NR SAN FR1 conditional handover for NTN less than 5MHz |
Samsung |
| R4-2504953 |
draftCR on requirments for less than 5MHz for NTN |
Huawei, HiSilicon |
| 7.10.3.5 |
RRM performance requirements |
|
| R4-2503324 |
Discussion on the performance part requirements for less than 5MHz NTN |
Xiaomi |
| R4-2503424 |
Discussion on less than 5MHz for NTN RRM performance requirements |
CATT |
| R4-2503663 |
Discussion on RRM performance requirements of Rel-19 NR-NTN in less than 5MHz |
Samsung |
| R4-2503797 |
Discussion on RRM performance requirements for less than 5MHz in NTN enhancement |
ZTECorporation,Sanechips |
| R4-2503898 |
Discussion on RRM test cases for less than 5MHz for NTN |
Huawei, HiSilicon |
| R4-2504446 |
RRM Performance Requirements for less than 5 MHz over NTN |
Nokia |
| 7.10.3.6 |
Demodulation performance requirements |
|
| R4-2503245 |
Discussions on demodulation performance requirements for NR-NTN with bandwidth less than 5MHz |
QUALCOMM Europe Inc. - Spain |
| R4-2503910 |
Discussion on Rel-19 NTN UE/SAN demodulation requirements for less than 5 MHz channel bandwidth |
Ericsson |
| R4-2504538 |
Discussion on NTN demodulation requirements for Less than 5MHz |
Samsung |
| 7.10.4 |
NTN testing for NGSO |
|
| R4-2504277 |
Discussion on NGSO channel modelling |
Nordic Semiconductor ASA |
| 7.10.4.1 |
Channel modeling |
|
| R4-2503159 |
Discussion on NTN NGSO Channel Model |
Nokia |
| R4-2503247 |
Discussions on channel modeling for NTN testing for NGSO |
QUALCOMM Europe Inc. - Spain |
| R4-2503710 |
Views on TE emulated channel model for satellite mobility |
Anritsu Corporation |
| R4-2504001 |
Discussion on NTN_testing_NGSO_channel_model |
ZTE Corporation, Sanechips |
| R4-2504174 |
Views on propagation delay correction |
ROHDE & SCHWARZ |
| R4-2504314 |
Discussion on NTN testing for NGSO channel model |
Huawei,HiSilicon |
| R4-2504344 |
TE-emulated channel model for NTN UE tests |
Ericsson |
| R4-2504349 |
Discussion on NSGO channel model for NTN testing |
MediaTek inc. |
| R4-2504536 |
Discussion on NTN testing NGSO channel model |
Samsung |
| 7.10.4.2 |
Demodulation performance requirements |
|
| R4-2503160 |
Discussion on NTN NGSO Performance Requirements |
Nokia |
| R4-2503246 |
Discussions on demodulation performance requirements for NTN testing for NGSO |
QUALCOMM Europe Inc. - Spain |
| R4-2504315 |
Discussion on less than 5MHz for NR NTN |
Huawei,HiSilicon |
| R4-2504345 |
UE demodulation requirements with time varying Doppler shift and propagation delay model |
Ericsson |
| R4-2504350 |
Discussions on demodulation performance requirements for NGSO channel model |
MediaTek inc. |
| R4-2504537 |
Discussion on demodulation requirement for NTN NGSO testing |
Samsung |
| 7.10.5 |
Moderator summary and conclusions |
|
| R4-2503615 |
Topic summary for [114bis][205] NR_IoT_NTN_req_test_enh |
Moderator (Xiaomi) |
| R4-2504635 |
Topic summary for [114bis][310] NR_IoT_NTN_less_than_5MHz_UERF |
Moderator (Xiaomi) |
| R4-2504636 |
Topic summary for [114bis][311] NR_IoT_NTN_less_than_5MHz_BSRF |
Moderator (Nokia) |
| R4-2504648 |
Topic summary for [114bis][323] NTN_testing_NGSO_channel_model_and_demod |
Moderator (Samsung) |
| R4-2504649 |
Topic summary for [114bis][324] NR_IoT_NTN_less_than_5MHz_demod |
Moderator (Ericsson) |
| R4-2504681 |
Topic summary for [114bis][123] NR_IoT_NTN_HPUE_part1 |
Moderator(Samsung) |
| R4-2504682 |
Topic summary for [114bis][124] NR_IoT_NTN_HPUE_part2 |
Moderator(Vivo) |
| R4-2504700 |
Way Forward for [114bis][323] NTN_testing_NGSO_channel_model_and_demod |
Samsung |
| R4-2504713 |
Way Forward for [114bis][310] NR_IoT_NTN_less_than_5MHz_UERF |
Xiaomi |
| R4-2504753 |
Way Forward for [114bis][324] NR_IoT_NTN_less_than_5MHz_demod |
Ericsson |
| R4-2504896 |
WF on RRM requirements for NR_IoT_NTN_req_test_enh |
Xiaomi |
| R4-2505113 |
WF on HPUE RF requirements for NR-NTN |
Samsung |
| R4-2505114 |
WF on HPUE RF requirements for IoT-NTN |
vivo |
| R4-2505160 |
Collection of simulation results for NTN HPUE |
Samsung, Xiaomi, Ericsson |
| 7.11.1 |
General aspects |
|
| R4-2503274 |
Draft CR for Operating bands including priority 2 cases |
Eutelsat Group |
| R4-2503940 |
NTN Ku-band - General aspects - bands |
Ericsson |
| R4-2504721 |
Draft CR for Operating bands including priority 2 cases |
Eutelsat Group |
| 7.11.2 |
Coexistence study based on ITU regulations |
|
| R4-2503320 |
Discussion the assumptions and parameters for NR NTN Ku Band coexistence study |
xiaomi |
| R4-2503454 |
Further discussion on coexistence evaluations for Ku-band for NR NTN |
CATT |
| R4-2504263 |
On co-existence simulation assumptions for NR NTN Ku band |
Ericsson |
| R4-2504264 |
On co-existence simulation results for NR NTN Ku band |
Ericsson |
| R4-2504338 |
On Ku-band coexsitence studies |
Samsung |
| R4-2504477 |
Discussion on Ku-band co-existence study |
SKY Perfect JSAT Corporation |
| R4-2504559 |
Discussion on coexistence simulation parameters for GEO and LEO VSAT |
SHARP Corporation |
| R4-2504658 |
Considerations for reducing Ku-band coexistence configurations |
THALES |
| 7.11.3 |
System parameters |
|
| R4-2503231 |
Ku Band: Further System Parameters incorporating 15 kHz Sub-carrier Spacing and lower Uplink A Band (Priority 2 Band Combination) |
Intelsat |
| R4-2503334 |
System parameters for Ku band(s) |
Xiaomi |
| R4-2503455 |
Further discussion on system parameters for Ku-band for NR NTN |
CATT |
| R4-2503740 |
Discussion on system parameters for NTN Ku band |
ZTE Corporation, Sanechips |
| R4-2503941 |
NTN Ku-band - System parameters |
Ericsson |
| R4-2504183 |
On Ku-band general requirements |
LG Electronics Finland |
| R4-2504278 |
Discussion on the asymmetric channel bandwidths support for NR NTN Ku band |
CHTTL, SKY Perfect JSAT Corporation, Intelsat |
| R4-2504280 |
Further discussion on the remaining system parameters for NR NTN Ku band with the inclusion of 15 kHz SCS |
CHTTL |
| R4-2504427 |
Draft CR for channel arrangement |
Eutelsat Group |
| R4-2504473 |
NR NTN system parameters for Ku band |
Nokia |
| 7.11.4 |
UE RF requirements |
|
| R4-2503335 |
Requirements for VSAT on Ku band(s) |
Xiaomi |
| R4-2503698 |
Discussion on VSAT requirements for NR NTN Ku band |
Huawei, HiSilicon |
| R4-2503741 |
Discussion on UE RF requirements for NTN Ku band |
ZTE Corporation, Sanechips |
| R4-2503942 |
NTN Ku-band - NTN VSAT RF requirements |
Ericsson |
| R4-2503944 |
Draft CR to 38101-5 - Needed updates to support NTN VSAT in FR1-NTN |
Ericsson |
| R4-2504212 |
On Ku-band NTN VSAT requirements |
LG Electronics Finland |
| R4-2504279 |
Discussion on NTN Ku band UE RF requirements |
MediaTek (Wuhan) Inc. |
| R4-2504281 |
Discussion on the minimum peak EIRP, EIS and the maximum input level requirement for the Rel.19 NTN Ku band VSAT |
CHTTL |
| 7.11.5 |
SAN RF core requirements |
|
| R4-2503456 |
Further discussion on SAN RF core requirements for Ku-band for NR NTN |
CATT |
| R4-2503742 |
Discussion on SAN RF requirements for NTN Ku band |
ZTE Corporation, Sanechips |
| R4-2503743 |
DraftCR to TS38.108 Add 10.4 and 10.5 requirements for NTN Ku bands |
ZTE Corporation, Sanechips |
| R4-2503943 |
NTN Ku-band - SAN requirements |
Ericsson |
| R4-2503945 |
Draft CR to 38108 - Needed updates to add a new SAN type in FR1-NTN |
Ericsson |
| R4-2504293 |
draft running CR to TS 38.108 the SAN requirement of the NR NTN Ku band |
CHTTL |
| R4-2504474 |
Discussion on NR NTN SAN requirement for Ku band |
Nokia |
| 7.11.6 |
RRM core requirements |
|
| R4-2503129 |
Discussion on RRM requirements for Ku bands for NR NTN |
MediaTek inc. |
| R4-2503139 |
Draft CR to 38.133 to modify uplink timing requirements to enable mobile VSAT served by NGSO |
Eutelsat Group, Thales, European Space Agency, Sharp, CHTTL, Airbus |
| R4-2503508 |
Ku Band RRM updates required to support FR1-NTN and FR2-NTN numerology |
Eutelsat Group |
| R4-2503706 |
Discussion on RRM requirements for Ku-band NTN |
LG Electronics Inc. |
| R4-2503794 |
Discussion on Ku bands for NR NTN |
ZTECorporation,Sanechips |
| R4-2503906 |
Discussion on RRM requirements for NTN in Ku band |
Huawei, HiSilicon |
| R4-2504449 |
Discussing on the adoption of VSAT Requirements for FR1-NTN |
Nokia |
| R4-2504532 |
RRM requirements for VSAT UE in Ku band |
Qualcomm Incorporated |
| 7.11.7 |
Moderator summary and conclusions |
|
| R4-2503616 |
Topic summary for [114bis][206] NR_NTN_Ku_bands |
Moderator (Apple) |
| R4-2504637 |
Topic summary for [114bis][312] NR_NTN_Ku_Band_General |
Moderator (Eutelsat) |
| R4-2504638 |
Topic summary for [114bis][313] NR_NTN_Ku_Band_Coexistence |
Moderator (Intelsat) |
| R4-2504639 |
Topic summary for [114bis][314] NR_NTN_Ku_Band_UE_SAN_RF |
Moderator (CHTTL) |
| R4-2504720 |
Way Forward for [114bis][314] NR_NTN_Ku_Band_UE_SAN_RF |
CHTTL |
| R4-2504722 |
Way Forward for [114bis][312] NR_NTN_Ku_Band_General |
Eutelsat |
| R4-2504723 |
Way Forward for [114bis][313] NR_NTN_Ku_Band_Coexistence |
Intelsat |
| R4-2504761 |
Way Forward for [114bis][312] NR_NTN_Ku_Band_General |
Eutelsat |
| R4-2504897 |
WF on RRM requirements for NR_NTN_Ku_bands |
Apple |
| 7.12.1 |
UE RF requirements |
|
| R4-2503586 |
On remaining issue for ATG RF requirement |
Apple |
| 7.12.1.1 |
Intra-band contiguous and inter-band CA |
|
| R4-2503396 |
Discussion on UE RF requirements for ATG with inter-band CA |
CMCC |
| R4-2503694 |
Discussion on Rel-19 ATG UE RF with DL inter-band CA_n3-n39 |
Huawei, HiSilicon |
| R4-2503723 |
Discussion for ATG UE RF requirements |
LG Electronics France |
| R4-2504038 |
Discussion on RF requirements of ATG UE inter-band CA |
Ericsson |
| R4-2504057 |
Discussion on Rel-19 ATG UE RF requirements |
Qualcomm Incorporated |
| R4-2504356 |
Discussion on RF requirement for Inter-band CA for ATG UE in Rel-19 |
ZTE Corporation, Sanechips |
| 7.12.1.2 |
UL MIMO |
|
| R4-2503395 |
Discussion on UE RF requirements for ATG with UL-MIMO |
CMCC |
| R4-2503695 |
Discussion on Rel-19 ATG UE RF with UL MIMO |
Huawei, HiSilicon |
| R4-2504039 |
Discussion on RF requirements of ATG UE UL MIMO |
Ericsson |
| R4-2504357 |
Discussion on RF requirement for UL-MIMO for ATG UE in Rel-19 |
ZTE Corporation, Sanechips |
| 7.12.2 |
BS RF requirements |
|
| R4-2503218 |
Draft CR for TS 38.141-1 to add ATG enhancement BS RF requirements |
Huawei, HiSilicon |
| R4-2503219 |
Draft CR for TS 38.141-2 to add ATG enhancement BS RF requirements |
Huawei, HiSilicon |
| R4-2503394 |
Discussion on BS RF requirements for ATG |
CMCC |
| R4-2503958 |
Clarification on the multi-band requirements for ATG BS CA |
ZTE Corporation, Sanechips |
| R4-2503959 |
draft CR to TS 38.104: the introduction of Rel-19 ATG BS supporting CA |
ZTE Corporation, Sanechips |
| 7.12.3 |
BS RF conformance requirements |
|
| R4-2503397 |
Draft CR for 38.141-2 to Introduce of R19 ATG enhancement BS RF requirements |
CMCC |
| R4-2503459 |
Draft CR for 38.141-1, Introduction of R19 ATG enhancement BS RF requirements |
CATT |
| R4-2503460 |
Draft CR for 38.141-2, Introduction of R19 ATG enhancement BS RF requirements |
CATT |
| R4-2503960 |
Discussion on the ATG BS CA conformance test |
ZTE Corporation, Sanechips |
| R4-2504040 |
Draft CR for 38.141-1 ATG BS test requirements |
Ericsson |
| R4-2504041 |
Draft CR for 38.141-2 ATG BS test requirements |
Ericsson |
| R4-2504042 |
Discussion on ATG BS DL test requirement |
Ericsson |
| R4-2504702 |
Draft CR for 38.141-1, Introduction of R19 ATG enhancement BS RF requirements |
CATT, ZTE Corporation, CMCC, Huawei, Ericsson |
| R4-2504703 |
Draft CR for 38.141-2 to Introduce of R19 ATG enhancement BS RF requirements |
CMCC, ZTE Corporation, Sanechips, CATT, Huawei, HiSilicon, Ericsson |
| 7.12.4 |
RRM core requirements for CA |
|
| R4-2503372 |
draftCR Introduce requirement applicability and cell re-selection requirement for ATG CA |
CMCC |
| R4-2503373 |
Discussion on RRM requirements for R19 ATG |
CMCC |
| R4-2503425 |
Draft CR to TS 38.133 on general measurement requirement for ATG |
CATT |
| R4-2503426 |
Draft CR to TS 38.133 on CSI-RS based L3 measurements for ATG |
CATT |
| R4-2503427 |
Discussion on enhancements for Rel-19 ATG RRM core requirements |
CATT |
| R4-2503587 |
draft CR on ATG UE RRM requirement |
Apple |
| R4-2503703 |
Discussion on RRM requirements for ATG CA operation |
LG Electronics Inc. |
| R4-2503704 |
Draft CR on L1-RSRP measurements for Reporting for ATG CA in Clause 9.5D |
LG Electronics Inc. |
| R4-2503878 |
Discussions on RRM core requirements for Rel-19 ATG |
Huawei, HiSilicon |
| R4-2503880 |
Draft CR on core requirements for Rel-19 ATG |
Huawei, HiSilicon |
| R4-2504014 |
Draft CR on core requirements for Rel-19 ATG |
Huawei, HiSilicon |
| R4-2504018 |
draftCR for MRTD and interruption requirements for ATG UE in R19 |
Intel Corporation |
| R4-2504244 |
Discussion on RRM aspects of R19 ATG |
ZTE Corporation, Sanechips |
| R4-2504254 |
Draft CR on intra-frequency measurement for R19 ATG |
ZTE Corporation, Sanechips |
| R4-2504255 |
Draft CR on inter-frequency measurement for R19 ATG |
ZTE Corporation, Sanechips |
| R4-2504461 |
Discussion on Remaining Issues Related to Rel-19 ATG CA in RRM Core |
Ericsson |
| R4-2504462 |
Draft CR for ATG Rel-19 Pre-configured measurement gap activation/deactivation delay |
Ericsson |
| R4-2504463 |
Draft CR for L1-SINR measurements for Reporting with ATG |
Ericsson |
| R4-2504925 |
Draft CR to TS 38.133 on general measurement requirement for ATG |
CATT |
| R4-2504926 |
Draft CR to TS 38.133 on CSI-RS based L3 measurements for ATG |
CATT |
| R4-2504927 |
draft CR on ATG UE RRM requirement |
Apple |
| R4-2504928 |
Draft CR on core requirements for Rel-19 ATG |
Huawei, HiSilicon |
| R4-2504929 |
draftCR for MRTD and interruption requirements for ATG UE in R19 |
Intel Corporation |
| R4-2504930 |
Draft CR on intra-frequency measurement for R19 ATG |
ZTE Corporation, Sanechips |
| R4-2504931 |
Draft CR on inter-frequency measurement for R19 ATG |
ZTE Corporation, Sanechips |
| R4-2504932 |
Draft CR for ATG Rel-19 Pre-configured measurement gap activation/deactivation delay |
Ericsson |
| R4-2504933 |
Draft CR for L1-SINR measurements for Reporting with ATG |
Ericsson |
| R4-2504941 |
draftCR Introduce requirement applicability and cell re-selection requirement for ATG CA |
CMCC |
| 7.12.5 |
RRM performance requirements |
|
| R4-2503374 |
Discussion on measurement accuracy and test cases for R19 ATG |
CMCC |
| R4-2503428 |
Discussion on enhancements for Rel-19 ATG RRM performance requirements |
CATT |
| R4-2503879 |
Discussions on RRM performance requirements for Rel-19 ATG |
Huawei, HiSilicon |
| R4-2504245 |
Discussion on RRM performance of R19 ATG |
ZTE Corporation, Sanechips |
| R4-2504464 |
Discussions on RRM Performance Enhancement Requirements for Rel-19 ATG CA |
Ericsson |
| 7.12.6 |
Demodulation performance requirements |
|
| R4-2503375 |
Discussion on demodulation and CSI requirements for Rel-19 ATG |
CMCC |
| R4-2504000 |
Discussion on Rel-19 ATG demodulation requirements |
ZTE Corporation, Sanechips |
| R4-2504384 |
Discussion on NR ATG enhancement for demodulation |
Ericsson |
| R4-2504443 |
On Enhancements for Air-to-ground network for NR |
Nokia |
| R4-2504540 |
View on BS demodulation requirement for ATG |
Samsung |
| 7.12.7 |
Moderator summary and conclusions |
|
| R4-2503617 |
Topic summary for [114bis][207] NR_ATG_enh |
Moderator (CMCC) |
| R4-2504630 |
Topic summary for [114bis][305] NR_ATG_enh |
Moderator (ZTE) |
| R4-2504683 |
Topic summary for [114bis][125] NR_ATG_enh |
Moderator(CMCC) |
| R4-2504691 |
Topic summary for [114bis][332] NR_ATG_enh_demod |
Moderator (CMCC) |
| R4-2504704 |
Way Forward for [114bis][305] NR_ATG_enh |
ZTE |
| R4-2504755 |
Way Forward for [114bis][332] NR_ATG_enh_demod |
CMCC |
| R4-2504760 |
Way Forward for [114bis][332] NR_ATG_enh_demod |
CMCC |
| R4-2504898 |
WF on RRM requirements for NR_ATG_enh |
CMCC |
| R4-2504924 |
Coffee break discussion minutes on NR_ATG_enh |
CMCC |
| R4-2505112 |
WF on UE RF requirements for NR ATG |
CMCC |
| 7.13.1 |
General aspects |
|
| R4-2503726 |
Rel-19 BS RF evolution overview |
Ericsson |
| 7.13.2 |
Expected EIRP mask for upper 6GHz |
|
| R4-2503577 |
[37.941] Incorrect MU data for n104 band |
ROHDE & SCHWARZ |
| R4-2503588 |
[37.941] Incorrect MU data for n104 band |
ROHDE & SCHWARZ |
| R4-2503589 |
[38.141-2] Incorrect MU data for n104 band |
ROHDE & SCHWARZ |
| R4-2503593 |
[38.141-2] Incorrect MU data for n104 band |
ROHDE & SCHWARZ |
| R4-2503601 |
[Not inc C1-1] PWS specific MU data to be included for n104 band |
ROHDE & SCHWARZ |
| R4-2503602 |
[C1-1 focus] Spec An MU to be updated for n104 band |
ROHDE & SCHWARZ |
| R4-2504433 |
Draft CR to TS 38.106 for introduction of expected EIRP mask core requirement for NCR |
Nokia, ZTE Corporation, Ericsson, Huawei, Samsung, Qualcomm, CATT |
| R4-2504436 |
Draft CR to TR 38.908 with updates to EEIRP sampling Error simulation results |
Nokia |
| R4-2504437 |
Draft CR to TR 38.908 with updates to test procedure |
Nokia |
| R4-2504513 |
Draft CR to TR 38-908: Corrections and Improvements related to EEIRP |
Ericsson |
| R4-2504736 |
Draft CR to TR 38.908 with updates to test procedure |
Nokia |
| R4-2504737 |
Draft CR to TR 38-908: Corrections and Improvements related to EEIRP |
Ericsson |
| R4-2504764 |
Draft CR to TR 38-908: Corrections and Improvements related to EEIRP |
Ericsson |
| 7.13.3 |
OTA test enhancement |
|
| R4-2504013 |
Simulation of BS-to-BS out-of-band isolation for edge-to-edge co-location isolation between 3.5 and 7 GHz |
Ericsson |
| R4-2504191 |
On OTA test enhancements |
Nokia |
| R4-2504358 |
Further discussion on OTA test enhancement |
ZTE Corporation, Sanechips |
| R4-2504594 |
Further discussion on CLTA related matters |
Huawei, HiSilicon |
| R4-2504596 |
Draft CR to TS 37.941: CLTA agreements |
Huawei, HiSilicon |
| 7.13.4 |
Transmitter co-existence spurious emission requirements |
|
| R4-2504192 |
On TX co-existence spurious emissions requirements |
Nokia |
| R4-2504267 |
On Co-existence parameters for BS Tx spurious emission co-existence requirement limits |
Ericsson |
| R4-2504298 |
Transmitter co-existence spurious emission requirements |
Huawei, HiSilicon |
| R4-2504343 |
Views on BS FR1 transmitter co-existence spurious emission requirements |
Qualcomm Germany |
| R4-2504359 |
Discussion on FR1 BS transmitter co-existence spurious emission requirements |
ZTE Corporation, Sanechips |
| 7.13.5.1 |
U6GHz BS EEIRP mask |
|
| R4-2504295 |
Further discussion on Expected EIRP test |
Huawei, HiSilicon |
| R4-2504296 |
Draft CR to TS 38.908 EEIRP measurement uncertainty |
Huawei, HiSilicon |
| R4-2504297 |
Draft CR to TS 38.141-2 EEIRP measurement uncertainty and coordinate alignment |
Huawei, HiSilicon |
| R4-2504360 |
Discussion on conformance testing for U6GHz BS EEIRP mask |
ZTE Corporation, Sanechips |
| R4-2504361 |
Draft CR to TS 38.141-2: MU value and angular transformation for U6GHz EEIRP mask |
ZTE Corporation, Sanechips |
| R4-2504362 |
Draft CR to TR 38.908 EEIRP measurement uncertainty and angular transformation |
ZTE Corporation, Sanechips |
| R4-2504363 |
Big Draft CR to TS 38.908: MU and others |
ZTE Corporation, Sanechips |
| R4-2504434 |
Draft CR to TS 38.115-2 for introduction of expected EIRP mask conformance test for NCR |
Nokia, ZTE Corporation, Ericsson, Huawei, Samsung, Qualcomm, CATT |
| R4-2504435 |
Draft CR to TS 38.141-2 with updates for EEIRP requirement conformance testing |
Nokia |
| R4-2504514 |
Draft CR to TS 38.141-2: Improvements related to Expected EIRP (EEIRP) |
Ericsson |
| R4-2504732 |
Draft CR to TS 38.908 EEIRP measurement uncertainty |
Huawei, HiSilicon |
| R4-2504733 |
Draft CR to TR 38.908 EEIRP measurement uncertainty and angular transformation |
ZTE Corporation, Sanechips |
| R4-2504734 |
Draft CR to TS 38.115-2 for introduction of expected EIRP mask conformance test for NCR |
Nokia, ZTE Corporation, Ericsson, Huawei, Samsung, Qualcomm, CATT |
| R4-2504735 |
Draft CR to TS 38.141-2 with updates for EEIRP requirement conformance testing |
Nokia |
| R4-2504738 |
Draft CR to TS 38.141-2: Improvements related to Expected EIRP (EEIRP) |
Ericsson |
| R4-2504765 |
Draft CR to TS 38.141-2: Improvements related to Expected EIRP (EEIRP) |
Ericsson |
| 7.13.5.2 |
Identification and reduction of BS OTA test scope |
|
| R4-2504012 |
OTA test scope reduction |
Ericsson |
| R4-2504299 |
OTA test case reduction |
Huawei, HiSilicon |
| R4-2504364 |
Discussion on the OTA testing scope reduction |
ZTE Corporation, Sanechips |
| R4-2504438 |
Further discussion BS OTA test scope reduction |
Nokia |
| 7.13.5.3 |
Simplification of BS TRP test methods |
|
| R4-2503167 |
Simplification of BS TRP test methods |
Nokia |
| R4-2504365 |
Discussion on the applicability improvement of TRP measurement |
ZTE Corporation, Sanechips |
| R4-2504515 |
TS 38.141-2 Annex I: Further discussion on improvement of TRP measurement methods |
Ericsson |
| R4-2504597 |
Information on European Commission feedback wrt. alternative test methods |
Huawei, HiSilicon |
| 7.13.6 |
Moderator summary and conclusions |
|
| R4-2504627 |
Topic summary for [114bis][302] NR_BS_RF_Part1_E_EIRP |
Moderator (ZTE) |
| R4-2504628 |
Topic summary for [114bis][303] NR_BS_RF_Part2_CLTA_SE |
Moderator (Huawei) |
| R4-2504629 |
Topic summary for [114bis][304] NR_BS_RF_Part3_OTA_TRP |
Moderator (ZTE) |
| R4-2504701 |
Way Forward for [114bis][303] NR_BS_RF_Part2_CLTA_SE |
Huawei |
| R4-2504739 |
Way Forward for [114bis][302] NR_BS_RF_Part1_E_EIRP |
ZTE |
| R4-2504740 |
Way Forward for [114bis][304] NR_BS_RF_Part3_OTA_TRP |
ZTE |
| R4-2504766 |
Way Forward for Tx spurious emissions co-existence limits re-evaluation |
Huawei |
| R4-2504769 |
Way Forward for Tx spurious emissions co-existence limits re-evaluation |
Huawei |
| 7.14.1 |
General aspects |
|
| R4-2504568 |
DraftCR to add min measurement distance for 50cm QZ |
Keysight Technologies UK Ltd |
| R4-2504758 |
DraftCR to add min measurement distance for 50cm QZ |
Keysight Technologies UK Ltd |
| 7.14.2.1 |
Test methodology for FR1 non-RedCap headworn XR devices |
|
| R4-2503136 |
Further discussion on XR test method |
Ericsson-LG Co., LTD |
| R4-2503498 |
on XR OTA tests |
Huawei, HiSilicon |
| R4-2503810 |
CR to TS38.161 for an alternate TRS and TRP test procedure for XR devices |
Apple |
| R4-2504440 |
Draft CR for split measurement grids method for TRP/TRS measurements |
Nokia, Keysight Technologies UK Ltd |
| R4-2504621 |
Discussion on OTA Test for XR Devices |
Meta |
| 7.14.2.2 |
Test methodology and radiated performance metric for FR1 NTN devices |
|
| R4-2503332 |
Discussion on OTA test for FR1 NTN devices |
Xiaomi |
| R4-2503496 |
on NTN OTA tests |
Huawei, HiSilicon |
| R4-2503551 |
On NTN OTA test methodology |
Apple |
| R4-2503552 |
draftCR to TR38.870 on NTN DUT usage scenario applicability |
Apple |
| R4-2503650 |
On OTA performance metric for handheld NTN UE |
Samsung |
| R4-2503651 |
Draft CR to TR 38.870 on NTN usage scenario and performance metric |
Samsung |
| R4-2503828 |
draft CR to 38.870 on NTN OTA performance metric and test method |
vivo |
| R4-2504058 |
Discussion on FR1 NTN devices OTA |
Qualcomm Incorporated |
| R4-2504182 |
Draft CR for split measurement grids method for TRP/TRS measurements |
Nokia, Keysight Technologies UK Ltd |
| R4-2504425 |
Draft CR for split measurement grids method for TRP/TRS measurements |
Nokia, Keysight Technologies UK Ltd |
| R4-2504578 |
On NTN OTA test methodology |
Apple |
| R4-2504579 |
draftCR to TR38.870 on NTN DUT usage scenario applicability |
Apple |
| R4-2504728 |
draft CR to 38.870 on NTN OTA performance metric and test method |
vivo |
| 7.14.2.3 |
FR1 dynamic MIMO OTA test methodology |
|
| R4-2503495 |
on MIMO OTA tests |
Huawei, HiSilicon |
| R4-2503652 |
On performance metric for FR1 dynamic MIMO |
Samsung |
| R4-2503809 |
On FR1 MIMO OTA Dynamic Channel Model |
Apple |
| R4-2503990 |
On Rel-19 MIMO OTA |
CAICT |
| R4-2503991 |
TR 38.762 V0.3.0 on MIMO OTA dynamic test methodology for FR1 UEs |
CAICT |
| R4-2504081 |
On dynamic MIMO OTA channel models reference target values |
CMCC |
| R4-2504566 |
TP for TR 38.762: Clarifications of Channel Models and Applicability |
Keysight Technologies UK Ltd, Spirent Communications, ETS-Lindgren, CAICT |
| R4-2504729 |
TP for TR 38.762: Clarifications of Channel Models and Applicability |
Keysight Technologies UK Ltd, Spirent Communications, ETS-Lindgren, CAICT |
| 7.14.3.1 |
TRP TRS requirements |
|
| R4-2503137 |
Discussion on Rel-19 TRP TRS requirements |
Ericsson-LG Co., LTD |
| R4-2503497 |
on TRP TRS OTA tests |
Huawei, HiSilicon |
| R4-2503653 |
On TRP TRS spec for narrow width UE |
Samsung |
| R4-2503811 |
Views on Rel-19 TRP TRS Performance Requirements |
Apple |
| R4-2503829 |
Updated working procedure for Rel-19 TRP TRS performance part |
vivo |
| R4-2504150 |
Discussion on TRP TRS requirements |
CAICT |
| R4-2504577 |
Proposals for Rel-19 TRP TRS requirements topic |
Telecom Italia S.p.A., Vodafone |
| 7.14.4 |
Moderator summary and conclusions |
|
| R4-2504653 |
Topic summary for [114bis][328] TRP_TRS_MIMO_OTA_Ph3 |
Moderator (vivo) |
| R4-2504730 |
Way Forward for [114bis][328] TRP_TRS_MIMO_OTA_Ph3 |
Vivo |
| R4-2504731 |
Ad-hoc meeting minutes for [114bis][328] TRP_TRS_MIMO_OTA_Ph3 |
Vivo |
| R4-2504763 |
Way Forward for [114bis][328] TRP_TRS_MIMO_OTA_Ph3 |
Vivo |
| 7.15.1 |
General aspects |
|
| R4-2503819 |
TP to TR 38.771 on the test procedure of sTxMP |
vivo |
| R4-2504061 |
TR 38.771v0.3.0 |
Qualcomm Incorporated |
| 7.15.2 |
RF testing methodology for FR2 non-handheld UE that can transmit simultaneously with multi-panel |
|
| R4-2503654 |
On remaining issues for STxMP test method |
Samsung |
| R4-2503818 |
Discussion on the FR2 OTA test method |
vivo |
| R4-2504059 |
Remaining issues for FR2 OTA test method on STxMP |
Qualcomm Incorporated |
| R4-2504060 |
TP to TR 38.771 on MU |
Qualcomm Incorporated |
| R4-2504567 |
TP for 38.771 on system related aspects |
Keysight Technologies UK Ltd |
| R4-2504726 |
TP to TR 38.771 on MU |
Qualcomm Incorporated, vivo |
| 7.15.3 |
Moderator summary and conclusions |
|
| R4-2504654 |
Topic summary for [114bis][329] NR_FR2_OTA |
Moderator (Qualcomm) |
| R4-2504727 |
Way Forward for [114bis][329] NR_FR2_OTA |
Qualcomm |
| 7.16.1 |
General aspects and work plan |
|
| R4-2503161 |
Discussion on SCM General Aspects |
Nokia |
| R4-2503509 |
TP on TR 38.753 Conclusions Chapter |
Nokia |
| R4-2503539 |
On general aspects of Spatial Channel Modeling study |
Apple |
| R4-2504177 |
TP to TR38753 on Spatial Channel Modeling for Demod - Annex |
Qualcomm Incorporated, Apple |
| R4-2504380 |
Discussion on NR SCM general issue |
Ericsson |
| R4-2504383 |
Draft TP for TR38.753 Chapter 7 on simulation results alignment |
Ericsson |
| R4-2504431 |
PMI statistics for measured MIMO channels in band n78 |
BT plc, Ericsson |
| R4-2504476 |
pCR for TR38.753 Chapter 7 on simulation results alignment |
Ericsson |
| 7.16.2 |
Spatial channel modelling methodology |
|
| R4-2503199 |
Big pCR for TR 38.753 |
Nokia |
| R4-2503206 |
TP to TR 38.753: Scope and reference |
China Telecom |
| R4-2503267 |
Discussion on spatial channel modelling |
MediaTek inc. |
| R4-2503268 |
Simulation results of spatial channel modelling |
MediaTek inc. |
| R4-2503269 |
TP to TR38.753: TDL approaches and related Annex |
MediaTek inc. |
| R4-2503461 |
TP for 38.753: on definitions of terms, symbols and abbreviations |
CATT |
| R4-2503540 |
Discussion on Spatial Channel Modeling Study |
Apple |
| R4-2503541 |
Simulation results for Spatial Channel Modeling study |
Apple |
| R4-2503542 |
Draft TP to TR 38.753 on SCM study - 5.1 CDL approach |
Apple, Qualcomm |
| R4-2503554 |
Discussion on Spatial Channel Model for Demodulation Performance Requirements |
Nokia |
| R4-2503555 |
Simulation Results and CDL Implementation for Spatial Channel Model for Demodulation Performance Requirements |
Nokia |
| R4-2503658 |
Discussion on spatial channel model for demodulation performance requirements |
Samsung |
| R4-2503659 |
Simulation results on spatial channel model |
Samsung |
| R4-2503660 |
TP for 38.753 on chapter 4 and chapter 2 |
Samsung |
| R4-2504002 |
Discussion on spatial channel model for demodulation performance requirements |
ZTE Corporation, Sanechips |
| R4-2504003 |
Simulation results on spatial channel model for demodulation performance requirements. |
ZTE Corporation, Sanechips |
| R4-2504004 |
TP for 38.753 introduction of spatial channel models for SU-MIMO PMI cases |
ZTE Corporation, Sanechips |
| R4-2504175 |
Discussion on CDL channel model |
ROHDE & SCHWARZ |
| R4-2504176 |
Views on SCM for demod |
Qualcomm Incorporated |
| R4-2504181 |
Simulation Results for SCM Demod |
Qualcomm Incorporated |
| R4-2504308 |
Discussion on spatial channel model for demodulation requirements |
Huawei,HiSilicon |
| R4-2504309 |
Simulation results on spatial channel model |
Huawei,HiSilicon |
| R4-2504310 |
Draft TP introduction of comparision of spatial channel models for SU-MIMO PDSCH cases |
Huawei,HiSilicon |
| R4-2504381 |
Discussion on NR SCM methodology for demodulation |
Ericsson |
| R4-2504382 |
Simulation results for NR SCM methodology |
Ericsson |
| R4-2504429 |
Results collection table for NR SCM |
BT plc |
| R4-2504430 |
Simulation Results for SCM Comparison and Alignment |
BT plc |
| R4-2504432 |
Channel Properties Comparison Methodologies |
BT plc |
| R4-2504616 |
TP for TR 38.753 Section 6.2 MU-MIMO |
BT plc |
| R4-2504617 |
TP for TR 38.753 Annex A Channel Measurements |
BT plc |
| R4-2504699 |
Discussion on spatial channel model for demodulation requirements |
Huawei,HiSilicon |
| R4-2504759 |
TP to TR38.753: TDL approaches and related Annex |
MediaTek inc. |
| R4-2504762 |
Simulation assumptions for SCM |
Huawei, HiSilicon, MediaTek |
| 7.16.3 |
Moderator summary and conclusions |
|
| R4-2504645 |
Topic summary for [114bis][320] NR_SCM |
Moderator (Nokia) |
| R4-2504695 |
Ad-hoc meeting minutes for [114bis][320] NR_SCM |
Nokia |
| R4-2504696 |
Way Forward for [114bis][320] NR_SCM |
Nokia |
| R4-2504697 |
Simulation assumptions for NR SCM |
Huawei |
| R4-2504698 |
Simulation collection for alignment of SCM |
Apple, Ericsson |
| R4-2504756 |
Way Forward for [114bis][320] NR_SCM |
Nokia |
| 7.17.1 |
General aspects |
|
| R4-2503530 |
Test case (performance part) plan for R19 RRM Phase 5 WI |
Apple, CATT |
| 7.17.2.1 |
FR2-1 L3 measurement delay by optimizing Rx beam sweeping factor |
|
| R4-2503251 |
FR2-1 L3 measurement delay reduction by optimizing RX beam sweeping factor |
Qualcomm Incorporated |
| R4-2503289 |
Remaining issues on FR2-1 L3 measurement delay by optimizing Rx beam sweeping factor |
vivo |
| R4-2503356 |
Discussion on FR2-1 L3 measurement delay by optimizing Rx beam sweeping factor |
OPPO |
| R4-2503357 |
DraftCR on Multi-Rx based RRC Connection Release with Redirection requirements |
OPPO |
| R4-2503416 |
Discussion on FR2-1 L3 measurement delay reduction by optimizing Rx beam sweeping factor |
CATT |
| R4-2503420 |
DraftCR on SSB-based intra-frequency measurement without gap delay reduction by optimizing Rx BSF |
CATT |
| R4-2503707 |
Discussion on RRM requirements for FR2-1 L3 measurement delay reduction |
LG Electronics Inc. |
| R4-2503763 |
Discussion on L3 measurement delay reduction by optimizing Rx beam sweeping factor |
CMCC |
| R4-2503779 |
DraftCR for optimizing Rx beam sweeping factor on SSB based Inter-frequency measurement with MG |
CMCC |
| R4-2503785 |
Discussions on FR2-1 SSB based L3 measurement delay reduction by optimizing Rx beam sweeping factor |
NTT DOCOMO, INC. |
| R4-2503862 |
Discussion on FR2-1 L3 measurement delay by optimizing Rx beam sweeping factor |
Huawei, HiSilicon |
| R4-2503911 |
Discussion on FR2-1 L3 measurement delay by optimizing Rx beam sweeping factor |
China Telecom |
| R4-2504020 |
Discussion on delay reduction by optimizing Rx beam sweeping factors |
Intel Corporation |
| R4-2504075 |
Draft CR HO requirements and FBS requirement applicability |
Nokia |
| R4-2504113 |
Discussion on FR2-1 L3 measurement delay by optimizing Rx beam sweeping factor |
Ericsson |
| R4-2504243 |
Discussion on Rx beam factor optimization of R19 RRM enhancements |
ZTE Corporation, Sanechips |
| R4-2504256 |
Draft CR on FBS based RRC Re-establishment for R19 RRM enh |
ZTE Corporation, Sanechips |
| R4-2504456 |
On FR2-1 L3 measurement delay by optimizing Rx beam sweeping factor |
Apple |
| R4-2504457 |
Draft CR on SSB based Intra-frequency measurement with MG |
Apple |
| R4-2504500 |
On L3 FBS requirements |
Nokia, Nokia Shanghai Bell |
| R4-2504565 |
Discussion on L3 measurement enhancement by optimizing Rx BSF |
Samsung |
| R4-2504600 |
Discussion on FR2-1 SSB based L3 measurement delay reduction by optimizing Rx beam sweeping factor |
MediaTek inc. |
| R4-2504657 |
draft CR for Rx beam sweeping optimization for SSB based Intra-frequency measurement with NCSG |
MediaTek Germany GmbH |
| R4-2504957 |
DraftCR on SSB-based intra-frequency measurement without gap delay reduction by optimizing Rx BSF |
CATT |
| R4-2504958 |
DraftCR for optimizing Rx beam sweeping factor on SSB based Inter-frequency measurement with MG |
CMCC |
| R4-2504959 |
Draft CR HO requirements and FBS requirement applicability |
Nokia |
| R4-2504960 |
Draft CR on FBS based RRC Re-establishment for R19 RRM enh |
ZTE Corporation, Sanechips |
| R4-2504970 |
Draft CR on SSB based Intra-frequency measurement with MG |
Apple |
| R4-2504971 |
draft CR for Rx beam sweeping optimization for SSB based Intra-frequency measurement with NCSG |
MediaTek Germany GmbH |
| 7.17.2.2 |
FR2-1 L3 measurement delay by optimizing CSSF outside gap in CA/DC |
|
| R4-2503250 |
Enhancement on FR2 CSSF |
Qualcomm Incorporated |
| R4-2503288 |
Remaining issues on FR 2-1 L3 measurement delay by optimizing CSSF outside gap in CA/DC |
vivo |
| R4-2503340 |
On optimizing CSSF for FR2-1 L3 measurement delay |
OPPO |
| R4-2503417 |
Discussion on FR2-1 L3 measurement delay reduction by optimizing CSSF outside gap in CADC |
CATT |
| R4-2503503 |
FR2-1 SSB based L3 measurement delay reduction with CSSF optimization |
Nokia, Nokia Shanghai Bell |
| R4-2503504 |
draftCR on CSSF optimization solutions |
Nokia, Nokia Shanghai Bell |
| R4-2503529 |
draft CR for Rel-19 CSSF enhancement solution 1 (one CC measurement per band) |
Apple, CATT, Huawei, HiSilicon, Qualcomm, Ericsson, ZTE, MediaTek, Samsung |
| R4-2503531 |
On FR2-1 L3 measurement delay by optimizing CSSF outside gap in CA/DC |
Apple |
| R4-2503764 |
Discussion on L3 measurement delay reduction by optimizing CSSF outside gap in CA/DC |
CMCC |
| R4-2503874 |
Discussion on FR2-1 L3 measurement delay by optimising CSSF outside gap in CA/DC |
Huawei, HiSilicon |
| R4-2503912 |
Discussion on FR2-1 L3 measurement delay by optimizing CSSF outside gap in CA/DC |
China Telecom |
| R4-2504021 |
Discussion on delay reduction by optimizing CSSF outside gap |
Intel Corporation |
| R4-2504114 |
Discussion on FR2-1 L3 measurement delay by optimizing CSSF outside gap in CA/DC |
Ericsson |
| R4-2504242 |
Discussion on CSSF optimization of R19 RRM enhancements |
ZTE Corporation, Sanechips |
| R4-2504601 |
Discussion on FR2-1 SSB based L3 measurement delay reduction by optimizing CSSF |
MediaTek inc. |
| 7.17.3 |
RRM core requirements of Fast SCell activation for UE supporting Rel-18 EMR |
|
| R4-2503568 |
draft CR for fast SCell activation for UE supporting Rel-18 EMR |
Apple |
| R4-2503753 |
Discusssion for fast scell activation for UE supporting Rel-18 EMR |
Ericsson |
| R4-2503765 |
Discussion on fast SCell activation for UE supporting Rel-18 EMR |
CMCC |
| R4-2503848 |
Discussion on the fast SCell activation for UE supporting Rel-18 EMR |
ZTE Corporation, Sanechips |
| R4-2503863 |
Discussion on maintenance for fast SCell activation based on EMR |
Huawei, HiSilicon |
| R4-2503864 |
Draft CR on fast SCell activation for UE supporting Rel-18 EMR |
Huawei, HiSilicon |
| R4-2504961 |
Draft CR on fast SCell activation for UE supporting Rel-18 EMR |
Huawei, HiSilicon |
| 7.17.4 |
RRM performance requirements of FR2-1 SSB based L3 measurement delay reduction for connected mode |
|
| R4-2503418 |
Discussion on performance requirements for FR2-1 L3 measurement delay reduction |
CATT |
| R4-2503505 |
draftCR on test case for intra-frequency measurement with CSSF solution 1 |
Nokia, Nokia Shanghai Bell |
| R4-2503646 |
Discussion on performance requirements of FR2-1 SSB based L3 measurement delay reduction for connected mode |
OPPO |
| R4-2503766 |
Discussion on RRM performance requirements of FR2-1 SSB based L3 measurement delay reduction for connected mode |
CMCC |
| R4-2503875 |
Discussion Discussion on performance part for FR2-1 SSB based L3 measurement delay reduction for connected mode |
Huawei, HiSilicon |
| R4-2503913 |
Discussion on RRM performance requirements of FR2-1 SSB based L3 measurement delay reduction for connected mode |
China Telecom |
| R4-2504076 |
On performance part of L3 measurement delay reduction |
Nokia, Nokia Shanghai Bell |
| R4-2504115 |
Discussion on performance requirements for FR2-1 L3 measurement enhancement |
Ericsson |
| 7.17.5 |
RRM performance requirements of Fast SCell activation for UE supporting Rel-18 EMR |
|
| R4-2503358 |
Discussion on performance requirements for fast SCell activation for UE supporting Rel-18 EMR |
OPPO |
| R4-2503419 |
Discussion on performance requirements of fast SCell activation for UE supporting R18 EMR |
CATT |
| R4-2503754 |
Discussion on performance part of the fast Scell activation for UE supporting Rel-18 EMR |
Ericsson |
| R4-2503767 |
Discussion on RRM performance requirements for fast SCell activation for UE supporting Rel-18 EMR |
CMCC |
| R4-2503849 |
Discussion on RRM performance requirements of Fast SCell activation for UE supporting Rel-18 EMR |
ZTE Corporation, Sanechips |
| R4-2503865 |
Discussion on performance part for Fast SCell activation for UE supporting Rel-18 EMR |
Huawei, HiSilicon |
| R4-2503914 |
Discussion on RRM performance requirements of Fast SCell activation for UE supporting Rel-18 EMR |
China Telecom |
| R4-2504518 |
Discussion on RRM performance requirements of Fast SCell activation for UE supporting Rel-18 EMR |
Nokia |
| 7.17.6 |
Moderator summary and conclusions |
|
| R4-2503618 |
Topic summary for [114bis][208] NR_RRM_Ph5_Part1 |
Moderator (Apple) |
| R4-2503619 |
Topic summary for [114bis][209] NR_RRM_Ph5_Part2 |
Moderator (CATT) |
| R4-2504899 |
WF on RRM requirements for NR_RRM_Ph5_Part1 |
Apple |
| R4-2504900 |
WF on RRM requirements for NR_RRM_Ph5_Part2 |
CATT |
| R4-2504916 |
Ad-hoc minutes for NR_RRM_Ph5 |
Apple |
| R4-2504940 |
Reply LS to RAN2 on granularity definition of pdcch-RACH-AffectedBandsList-r18 |
MediaTek |
| R4-2504962 |
LS on Rx BSF optimization for NR RRM Ph5 |
CATT |
| 7.18.1 |
General aspects |
|
| R4-2503202 |
Updated work plan for NR demodulation performance Phase 5 |
China Telecom |
| R4-2503909 |
On general issues for Rel-19 MMSE-IRC receiver under interference |
Ericsson |
| R4-2503924 |
Discussion on general topics for 8Rx UE with MMSE-IRC |
Nokia |
| 7.18.2 |
UE demodulation performance requirements for 8Rx with MMSE-IRC |
|
| R4-2503140 |
Discussion on UE demodulation requirements with 8Rx MMSE-IRC receiver |
MediaTek inc. |
| R4-2503141 |
Simulation results for UE demodulation requirements with 8Rx MMSE-IRC receiver |
MediaTek inc. |
| R4-2503203 |
Discussion on UE demodulation performance requirements for 8Rx with MMSE-IRC |
China Telecom |
| R4-2503376 |
Simulation results for 8Rx UE interference suppressing |
CMCC |
| R4-2503377 |
Discussion on interference suppressing performance for 8Rx UE |
CMCC |
| R4-2503543 |
On UE demodulation performance requirements with 8RX |
Apple |
| R4-2503544 |
Simulation results for ICI and MU-MIMO with 8RX |
Apple |
| R4-2503545 |
Summary of simulation results for ICI and MU-MIMO with 8RX |
Apple |
| R4-2503661 |
Discussion on UE demodulation and CSI performance requirements for 8Rx with MMSE-IRC |
Samsung |
| R4-2503925 |
Discussion on UE demodulation performance requirements for 8Rx with MMSE-IRC |
Nokia |
| R4-2503926 |
Simulations for UE demodulation performance requirements for 8Rx with MMSE-IRC |
Nokia |
| R4-2503995 |
Discussion on UE demodulation performance requirements for 8Rx with MMSE-IRC |
ZTE Corporation, Sanechips |
| R4-2503996 |
Simulation results on UE demodulation performance requirements for 8Rx with MMSE-IRC |
ZTE Corporation, Sanechips |
| R4-2504304 |
Discussion on 8Rx MMSE-IRC requirements |
Huawei,HiSilicon |
| R4-2504305 |
Simulation results on 8Rx MMSE-IRC requirements |
Huawei,HiSilicon |
| R4-2504327 |
On MMSE-IRC receiver for interference mitigation with 8Rx |
Ericsson |
| R4-2504328 |
Simulation results for MMSE-IRC receiver for 8Rx reception |
Ericsson |
| R4-2504519 |
Views on 8Rx UE demodulation and CSI requirements with inter-cell and intra-cell inter-user interference |
Qualcomm |
| 7.18.3 |
BS demodulation performance requirements for MMSE-IRC |
|
| R4-2503204 |
Simulation results on BS demodulation performance requirements for MMSE-IRC |
China Telecom |
| R4-2503205 |
Discussion on BS demodulation performance requirements for MMSE-IRC |
China Telecom |
| R4-2503275 |
Discussion on BS demodulation performance requirement using MMSE-IRC |
Tejas Network Limited |
| R4-2503378 |
Simulation results for BS interference suppressing with MMSE-IRC |
CMCC |
| R4-2503379 |
Discussion on BS demodulation requirements for interference suppressing with MMSE-IRC receiver |
CMCC |
| R4-2503452 |
Further discussion on BS demodulation performance for MMSE-IRC |
CATT |
| R4-2503453 |
Simulation results for BS requirement with MMSE_IRC receiver |
CATT |
| R4-2503712 |
Simulation Results – NR BS Demodulation Performance Requirements for MMSE-IRC |
Tejas Network Limited |
| R4-2503907 |
Discussion on Rel-19 MMSE-IRC BS demodulation requirements |
Ericsson |
| R4-2503908 |
Simulation results for Rel-19 MMSE-IRC BS demodulation requirements |
Ericsson |
| R4-2503997 |
Discussion on BS demodulation performance for MMSE-IRC |
ZTE Corporation, Sanechips |
| R4-2503998 |
Simulation results on BS demodulation performance for MMSE-IRC |
ZTE Corporation, Sanechips |
| R4-2504306 |
Discussion on BS MMSE-IRC requirements with inter-cell interference |
Huawei,HiSilicon |
| R4-2504307 |
Simulation results on BS MMSE-IRC requirements with inter-cell interference |
Huawei,HiSilicon |
| R4-2504342 |
Views on BS demodulation requirements for MMSE-IRC |
Qualcomm Germany |
| R4-2504441 |
NR Demodulation Performance Phase 5: BS demodulation performance requirements for MMSE-IRC |
Nokia |
| R4-2504442 |
Simulation Results – NR BS Demodulation Performance Requirements for MMSE-IRC |
Nokia |
| R4-2504521 |
Discussion on BS demodulation for NR MMSE-IRC. |
NTT DOCOMO, INC. |
| R4-2504533 |
Simulation results summary for BS requirement with MMSE-IRC receiver |
Samsung |
| R4-2504534 |
View on the remaining issue for BS demodulation requirement with MMSE-IRC receiver |
Samsung |
| R4-2504535 |
Simulation results on BS demodulation requirement with MMSE-IRC receiver |
Samsung |
| 7.18.4 |
Moderator summary and conclusions |
|
| R4-2504646 |
Topic summary for [114bis][321] NR_demod_Ph5_Part1_General_BS |
Moderator (China Telecom) |
| R4-2504647 |
Topic summary for [114bis][322] NR_demod_Ph5_Part2_UE |
Moderator (Nokia) |
| R4-2504692 |
Way Forward for [114bis][321] NR_demod_Ph5_Part1_General_BS |
China Telecom |
| R4-2504693 |
Ad-hoc meeting minutes for [114bis][322] NR_demod_Ph5_Part2_UE |
Nokia |
| R4-2504694 |
Way Forward for [114bis][322] NR_demod_Ph5_Part2_UE |
Nokia |
| R4-2504757 |
Way Forward for [114bis][321] NR_demod_Ph5_Part1_General_BS |
China Telecom |
| R4-2504768 |
Way Forward for [114bis][321] NR_demod_Ph5_Part1_General_BS |
China Telecom |
| 7.19.1 |
General aspects |
|
| R4-2503227 |
Discussion on General Aspects for AI/ML Air Interface |
Korea Testing Laboratory |
| R4-2503229 |
Discussion on general aspects of AIML for NR air interface |
CAICT |
| R4-2503253 |
Generalization aspects of AI-ML |
Qualcomm Incorporated |
| R4-2503306 |
Discussion on general aspect for AI |
Xiaomi |
| R4-2503514 |
Discussion on General Aspects on AI/ML for NR Air Interface |
Apple |
| R4-2503770 |
Discussion on general aspects |
CMCC |
| R4-2503920 |
On general issues for AIML |
Ericsson |
| R4-2504229 |
General aspects of AI/ML for NR Air interface |
Nokia |
| R4-2504316 |
Discussion on general aspects on AIML for NR air interface |
Huawei,HiSilicon |
| 7.19.2 |
CSI reporting requirement and testing framework for CSI prediction |
|
| R4-2503252 |
CSI Prediction: Simulation results and core requirements |
Qualcomm Incorporated |
| R4-2503270 |
Discussion on CSI reporting requirement framework for CSI prediction |
MediaTek inc. |
| R4-2503406 |
Discussion on CSI reporting requirement framework for CSI prediction |
CATT |
| R4-2503517 |
Discussion on CSI Prediction: CSI reporting requirement framework for CSI prediction |
Apple |
| R4-2503769 |
Discussion on CSI prediction |
CMCC |
| R4-2504005 |
Discussion on CSI reporting requirement and testing framework for CSI prediction. |
ZTE Corporation, Sanechips |
| R4-2504022 |
Discussion on CSI reporting requirement and testing framework for CSI prediction |
vivo |
| R4-2504235 |
CSI reporting requirement and testing framework for CSI prediction |
OPPO |
| R4-2504317 |
Discussion on CSI reporting requirement framework for AIML CSI prediction |
Huawei,HiSilicon |
| R4-2504346 |
Discussion on CSI prediction |
Ericsson |
| R4-2504539 |
View on CSI reporting requirements framework for CSI prediction |
Samsung |
| R4-2504541 |
CSI reporting requirement and testing framework for CSI prediction |
Nokia |
| 7.19.3 |
RRM core requirement and testing framework for beam management |
|
| R4-2503230 |
Discussion on RRM core requirements for beam management |
CAICT |
| R4-2503257 |
On DL Tx Hierarchy Beamforming Codebook Design and the Prediction Impact |
NTU |
| R4-2503307 |
Discussion on core part requirement and testing framework for AI beam management |
Xiaomi |
| R4-2503407 |
Discussion on RRM core requirements testing framework for BM |
CATT |
| R4-2503515 |
Discussion on Beam Management: RRM core requirement and testing framework for beam management |
Apple |
| R4-2503553 |
RRM Core Requirements for AI/ML Beam Management |
Qualcomm Incorporated |
| R4-2503606 |
Discussion on RRM core requirement and testing framework for beam management |
MediaTek Inc. |
| R4-2503701 |
RRM core requirement and testing framework for beam management |
Tejas Network Limited |
| R4-2503711 |
FR2 test setup for AI/ML beam management evaluation |
Anritsu Corporation |
| R4-2503768 |
Discussion on RRM requirements for beam management |
CMCC |
| R4-2503786 |
Discussions on RRM core requirement for beam management |
NTT DOCOMO, INC. |
| R4-2503789 |
Discussion on the RRM requirements of AI/ML Beam management |
ZTECorporation,Sanechips |
| R4-2504023 |
Discussion on RRM core requirement and testing framework for beam management |
vivo |
| R4-2504055 |
Testability for AI/ML beam management |
Qualcomm Incorporated |
| R4-2504107 |
Discussion on RRM core requirements and test framework for beam management |
Ericsson |
| R4-2504216 |
Discussion on RRM core requirements and testing framework for AI-BM |
Samsung |
| R4-2504230 |
RRM core requirement and testing framework for beam management |
Nokia |
| R4-2504238 |
RRM core requirement and testing framework for beam management |
OPPO |
| R4-2504268 |
Discussion on test setup for AI/ML based beam management |
Rohde & Schwarz |
| R4-2504318 |
Discussion on RRM core requirement and testing framework for AIML Beam management |
Huawei,HiSilicon |
| R4-2505092 |
RRM Core Requirements for AI/ML Beam Management |
Qualcomm Incorporated |
| 7.19.4 |
RRM core requirement and testing framework for Positioning accuracy enhancement |
|
| R4-2503254 |
RRM Core Requirements for Positioning Accuracy |
Qualcomm Incorporated |
| R4-2503408 |
Discussion on RRM core requirements testing framework for positioning |
CATT |
| R4-2503518 |
Discussion on RRM Core Requirements for positioning accuracy enhancement |
Apple |
| R4-2503771 |
Discussion on RRM requirements for positioning accuracy enhancement |
CMCC |
| R4-2503790 |
Discussion on the RRM requirements of AI/ML positioning |
ZTECorporation,Sanechips |
| R4-2503927 |
On requirements for AI/ML based positioning |
Ericsson |
| R4-2504024 |
Discussion on RRM core requirement and testing framework for Positioning accuracy enhancement |
vivo |
| R4-2504237 |
RRM core requirement and testing framework for Positioning |
OPPO |
| R4-2504319 |
Discussion on RRM core requirement and testing framework for AIML Positioning |
Huawei,HiSilicon |
| R4-2504542 |
RRM core requirements and testing framework for AI/ML positioning accuracy enhancement |
Nokia |
| 7.19.5 |
Moderator summary and conclusions |
|
| R4-2504684 |
Topic summary for [114bis][126] NR_AIML_air_part1 |
Moderator(Qualcomm) |
| R4-2505105 |
WF on requirements for AI/ML air interface normative work |
Qualcomm |
| R4-2505106 |
Ad hoc minutes on AI/ML air interface |
Qualcomm |
| R4-2505151 |
Collection of simulation results for AI/ML BM |
vivo |
| R4-2505152 |
Updated simulation assumptions for AI/ML BM |
vivo, NTU, Nokia, Ericsson, Qualcomm, Xiaomi, Huawei, Hisilicon, Mediatek, OPPO, APPLE, Rohde & Schwarz, CATT, Samsung, Intel, ZTE Corporation, Sanechips, CAICT |
| R4-2505153 |
Collection of simulation result for AI/ML CSI prediction |
OPPO |
| R4-2505154 |
Updated simulation assumptions for AI/ML CSI prediction |
OPPO |
| R4-2505229 |
Updated simulation assumptions for AI/ML CSI prediction |
OPPO, CAICT, vivo, Nokia, Ericsson, Qualcomm, CMCC, CTC, Huawei, Hisilicon, Mediatek, CATT, Samsung, ZTE Corporation, Apple |
| 7.20.1 |
General aspects |
|
| R4-2503409 |
Discussion on general aspects for AIML for NR air |
CATT |
| R4-2503519 |
General aspects for NR Air Interface |
Apple |
| R4-2503772 |
Discussion on general aspects for study on AI/ML |
CMCC |
| R4-2504025 |
Discussion on general aspects for AI/ML for NR air interface Phase 2 |
vivo |
| R4-2504215 |
On General Aspects of AI/ML for NR Air Interface Phase 2 |
Nokia |
| R4-2504320 |
Discussion on general aspects on AIML for NR air interface phase 2 |
Huawei,HiSilicon |
| 7.20.2 |
Testing issues for CSI compression two-sided models |
|
| R4-2503255 |
CSI Compression: Testability and Interoperability |
Qualcomm Incorporated |
| R4-2503258 |
On AI/ML Interoperability and Standardization of Testing and Verification for CSI Use Case – A PCA based approach |
NTU |
| R4-2503271 |
Discussion on Testing issues for CSI compression two-sided models |
MediaTek inc. |
| R4-2503410 |
Discussion on testing issues for CSI compression two-sided models |
CATT |
| R4-2503516 |
Study on CSI Compression: Testability and Interoperability issues |
Apple |
| R4-2503773 |
Discussion on testing issues for CSI compression two-sided models |
CMCC |
| R4-2504006 |
Discussion on Testing issues for CSI compression two-sided models |
ZTE Corporation, Sanechips |
| R4-2504026 |
Discussion on testing issues for CSI compression two-sided models |
vivo |
| R4-2504217 |
Study on testing issues for CSI compression two-sided models |
Samsung |
| R4-2504231 |
Testing issues for CSI compression two-sided models |
Nokia |
| R4-2504236 |
Testing issues for CSI compression two-sided models |
OPPO |
| R4-2504321 |
Discussion on testing issues for CSI compression two-sided models |
Huawei,HiSilicon |
| R4-2504439 |
Two sided CSI compression |
Ericsson |
| 7.20.3 |
Moderator summary and conclusions |
|
| R4-2504685 |
Topic summary for [114bis][127] NR_AIML_air_part2 |
Moderator(Ericsson) |
| R4-2505107 |
WF on AI/ML air interfance study |
Ericsson |
| R4-2505108 |
Ad hoc minutes on AI/ML air interface study |
Ericsson |
| R4-2505155 |
Collection of simulation results for AI/ML CSI compression |
Huawei |
| R4-2505156 |
Simulation assumptions on AI/ML CSI compression |
Huawei, Hisilicon, OPPO, CATT, Vivo, NTU, Nokia, Ericsson, Qualcomm, Xiaomi, Mediatek, APPLE, Rohde & Schwarz, Samsung, Intel, ZTE Corporation, Sanechips, CAICT |
| 7.21.1 |
General aspects |
|
| R4-2503350 |
Discussion on general aspects for AI mobility |
OPPO |
| R4-2503521 |
General aspects on AI/ML for mobility in NR |
Apple |
| R4-2503645 |
TP on RAN4 aspects for TR 38.744 |
OPPO |
| R4-2503774 |
Discussion on general part for AI/ML for mobility |
CMCC |
| R4-2503850 |
Discussion on General Aspects of AIML Mobility |
ZTE Corporation, Sanechips |
| R4-2503886 |
Discussion on genereal aspects in AIML mobility |
Huawei, HiSilicon |
| R4-2503928 |
General discussion on AI/ML for mobility |
Ericsson |
| R4-2504046 |
Discussion on general aspects for AI mobility |
vivo |
| R4-2504288 |
Discussion on AI mobility general and scope |
Samsung |
| R4-2504954 |
TP on RAN4 aspects for TR 38.744 |
OPPO |
| R4-2504963 |
TP on skeleton of RAN4 aspects for TR 38.744 |
OPPO |
| 7.21.2 |
Study of impacts on RAN4 requirements |
|
| R4-2503705 |
Study of impacts on RAN4 requirements for AIML mobility in NR |
Tejas Network Limited |
| 7.21.2.1 |
Study of RAN4 impacts for RRM measurement prediction |
|
| R4-2503308 |
Discussion on impacts on RAN4 requirement for RRM measurement prediction in AI mobility |
Xiaomi |
| R4-2503351 |
Study of impacts on RAN4 requirements for RRM measurement prediction |
OPPO |
| R4-2503411 |
Discussion on impacts of AIML RRM measurement prediction on RRM requirements |
CATT |
| R4-2503522 |
Study of RAN4 impacts for RRM measurement prediction for AIML Mobility in NR |
Apple |
| R4-2503582 |
Discussion of RAN4 impacts for RRM measurement prediction |
LG Electronics Inc. |
| R4-2503607 |
Discussion on RAN4 impacts for RRM measurement prediction |
MediaTek Inc. |
| R4-2503775 |
Discussion on RAN4 impacts for RRM measurement prediction |
CMCC |
| R4-2503787 |
Discussions on RRM measurement impacts of AIML for mobility |
NTT DOCOMO, INC. |
| R4-2503851 |
Discussion impacts on requirements of AI/ML mobility |
ZTE Corporation, Sanechips |
| R4-2503887 |
Discussion on impacts for RRM measurement prediction |
Huawei, HiSilicon |
| R4-2503929 |
On requirements for RRM measurement prediction for AI/ML based mobility |
Ericsson |
| R4-2504047 |
Discussion on RAN4 impacts for RRM measurement prediction |
vivo |
| R4-2504232 |
Study of RAN4 impacts for RRM measurement prediction |
Nokia |
| R4-2504287 |
General discussion on AI mobility regarding RAN4 requirements impact |
Samsung |
| R4-2504524 |
Impact of AI based mobility on RRM measurement prediction |
Qualcomm Incorporated |
| 7.21.2.2 |
Study of RAN4 impacts for measurement event prediction |
|
| R4-2503309 |
Discussion on impacts on RAN4 requirement for measurement event prediction in AI mobility |
Xiaomi |
| R4-2503352 |
Study of impacts on RAN4 requirements for measurement event prediction |
OPPO |
| R4-2503412 |
Discussion on impacts of AIML measurement event prediction on RRM requirements |
CATT |
| R4-2503523 |
Study of RAN4 impacts for measurement event prediction for AIML Mobility in NR |
Apple |
| R4-2503608 |
Discussion on RAN4 impacts for measurement event prediction |
MediaTek Inc. |
| R4-2503776 |
Discussion on RAN4 impacts for measurement event prediction |
CMCC |
| R4-2503852 |
Discussion on impacts for measurement event prediction |
ZTE Corporation, Sanechips |
| R4-2503888 |
Discussion on impacts for measurement event prediction |
Huawei, HiSilicon |
| R4-2503930 |
On requirements for Event prediction for AI/ML based mobility |
Ericsson |
| R4-2504048 |
Discussion on RAN4 impacts for measurement event prediction |
vivo |
| R4-2504233 |
Study of RAN4 impacts for measurement event prediction |
Nokia |
| R4-2504525 |
Impact of AI based mobility on RRM event prediction |
Qualcomm Incorporated |
| 7.21.3 |
Study of testability and interoperability |
|
| R4-2503300 |
Discussion on study of testability and interoperability for AIML mobility |
Xiaomi |
| R4-2503353 |
Study of testability and interoperability for AI mobility |
OPPO |
| R4-2503413 |
Discussion on testability and interoperability issues for AIML mobility |
CATT |
| R4-2503520 |
On Testability and Interoperability Issues for AIML Mobility in NR |
Apple |
| R4-2503609 |
Discussion on testability and interoperability of AI mobility |
MediaTek Inc. |
| R4-2503777 |
Discussion on testability and interoperability for AI/ML for mobility |
CMCC |
| R4-2503853 |
Discussion on the interoperability and testability aspects |
ZTE Corporation, Sanechips |
| R4-2503889 |
Discussion on testability and interoperability issues in AIML mobility |
Huawei, HiSilicon |
| R4-2503931 |
On testing of AI/ML based mobility |
Ericsson |
| R4-2504049 |
Discussion on testability and interoperability for AI mobility |
vivo |
| R4-2504234 |
Study of testability and interoperability on AI/ML Mobility |
Nokia |
| R4-2504286 |
General discussion on AI mobility regarding testability and interoperability |
Samsung |
| R4-2504526 |
Testability and data consistency |
Qualcomm Incorporated |
| 7.21.4 |
Moderator summary and conclusions |
|
| R4-2503620 |
Topic summary for [114bis][210] FS_NR_AIML_Mob |
Moderator (Nokia) |
| R4-2504901 |
WF on RRM requirements for FS_NR_AIML_Mob |
Nokia |
| 7.22 |
NR MIMO Phase 5 |
|
| R4-2504917 |
Ad-hoc minutes for FS_NR_AIML_Mob |
Nokia |
| 7.22.1 |
General aspects |
|
| R4-2504169 |
R19 on power class for 3T |
OPPO |
| 7.22.2 |
UE RF requirements |
|
| R4-2503172 |
On the UE RF requirement for the FR2 asymmetric connection scenario |
Qualcomm, Sony, Nokia |
| R4-2503173 |
dCR on RF requirements for a UE with different TCI states for UL and DL |
Qualcomm, Sony, Nokia |
| R4-2503510 |
3Tx NR specifications |
Qualcomm Technologies |
| R4-2503844 |
Further discussion of UE RF impact for NR MIMO phase 5 |
vivo |
| R4-2504090 |
On RF requirements for Rel-19 NR-MIMO |
Huawei, HiSilicon |
| R4-2504168 |
R19 MPR for 3Tx |
OPPO |
| R4-2504390 |
UE RF requirements of NR MIMO Phase 5 |
Samsung |
| R4-2504581 |
On the UE RF requirements for NR MIMO Phase 5 |
Ericsson |
| 7.22.3.1 |
Enhancement for UE-initiated/event-driven beam management |
|
| R4-2503127 |
Views for enhanced UE-initiated/event-driven beam management |
Qualcomm Technologies Ireland |
| R4-2503312 |
Discussion on UE-initiated/event-driven beam management on Rel-19 MIMO phase 5 |
Xiaomi |
| R4-2503546 |
On RRM Requirements for UE initiated beam management |
Apple |
| R4-2503598 |
Discussion on RRM requirements of UE-initiated/event-driven beam management |
LG Electronics |
| R4-2503665 |
Discussion on RRM requirements of UE-initiated beam management in Rel-19 MIMO phase 5 |
Samsung |
| R4-2503755 |
Discussion on RRM requirements for event-driven beam management for NR MIMO Phase 5 |
CMCC |
| R4-2503869 |
Discussion on RRM impact for Rel-19 MIMO on UE initiated BM |
Huawei, HiSilicon |
| R4-2503934 |
Discussion on UE-initiated/event-driven beam management |
Ericsson |
| R4-2504073 |
On NR MIMO Phase 5 UEIBM requirements |
Nokia |
| R4-2504074 |
DraftCR for UEIBM reporting requirements |
Nokia |
| R4-2504248 |
Discussion on RRM aspects of UE-initiated beam management of R19 NR MIMO Phase 5 |
ZTE Corporation, Sanechips |
| R4-2504602 |
Discussion on R19 MIMO for UE-initiated/event-driven beam management |
MediaTek inc. |
| 7.22.3.2 |
Other RRM requirements |
|
| R4-2503128 |
Views on additional RRM requirements for NR MIMO Phase 5 |
Qualcomm Technologies Ireland |
| R4-2503313 |
Discussion on other RRM requirement on Rel-19 MIMO phase 5 |
Xiaomi |
| R4-2503547 |
On RRM Requirements for MIMO Phase 5 |
Apple |
| R4-2503666 |
Discussion on RRM requirements of other aspects in Rel-19 MIMO phase 5 |
Samsung |
| R4-2503756 |
Discussion on other RRM requirements for NR MIMO Phase 5 |
CMCC |
| R4-2503876 |
Discussion on RRM impact for Rel-19 MIMO on other aspect |
Huawei, HiSilicon |
| R4-2503877 |
Discussion on simulation results of CJT calibration |
Huawei, HiSilicon |
| R4-2503935 |
Discussion on CJTC reporting and asymmteric UL TRP requirements |
Ericsson |
| R4-2504249 |
Discussion on other RRM aspects of R19 NR MIMO Phase 5 |
ZTE Corporation, Sanechips |
| R4-2504501 |
Other RRM requirements for MIMO ph5 |
Nokia |
| R4-2504502 |
Draft CR for UL only TRP TCI state switching |
Nokia |
| R4-2504503 |
Simulation results for CJT RRM requirements |
Nokia |
| R4-2504603 |
Discussion on R19 MIMO for other RRM requirements |
MediaTek inc. |
| 7.22.4 |
Moderator summary and conclusions |
|
| R4-2503621 |
Topic summary for [114bis][211] NR_MIMO_Ph5_Part1 |
Moderator (Samsung) |
| R4-2503622 |
Topic summary for [114bis][212] NR_MIMO_Ph5_Part2 |
Moderator (MediaTek) |
| R4-2504686 |
Topic summary for [114bis][128] NR_MIMO_Ph5_UE |
Moderator(Samsung) |
| R4-2504902 |
WF on RRM requirements for NR_MIMO_Ph5_Part1 |
Samsung |
| R4-2504903 |
WF on RRM requirements for NR_MIMO_Ph5_Part2 |
MediaTek |
| R4-2504918 |
Ad-hoc minutes for NR_MIMO_Ph5 |
Samsung |
| R4-2504939 |
Coffee break discussion minutes for NR_MIMO_Ph5 |
Samsung |
| R4-2504955 |
Collection of simulation results for CJT calibration in NR_MIMO_Ph5_Part2 |
MediaTek |
| R4-2505111 |
WF on UE RF requirements for MIMO enhancement phase5 |
Samsung |
| 7.23.1 |
General aspects (including RAN4 aspects for SBFD system parameters) |
|
| R4-2503235 |
Fair coexistence between SBFD and TDD networks |
Charter Communications, Inc |
| R4-2503285 |
Discussion on SBFD General aspects |
Tejas Network Limited |
| R4-2503405 |
Discussion on SBFD general part |
CMCC |
| R4-2503466 |
Discussion on SBFD general issues |
CATT |
| R4-2503823 |
Discussion on the subband configurations and guardbands for gNB SBFD |
vivo |
| R4-2504007 |
SBFD general aspects |
Ericsson |
| R4-2504011 |
Draft CR to 38.104 for introduction of SBFD |
Ericsson |
| R4-2504043 |
Discussion on MPR impact on SBFD UL resource muting |
Ericsson |
| R4-2504091 |
On general aspects for SBFD |
Huawei, HiSilicon |
| R4-2504193 |
On SBFD system parameters |
Nokia |
| R4-2504218 |
Further discussion on general aspects for SBFD system |
Samsung |
| R4-2504339 |
Views on general aspects for SBFD |
Qualcomm Germany |
| R4-2504368 |
Discussion on system parameters for SBFD BS |
ZTE Corporation, Sanechips |
| R4-2504455 |
RF impact due to UL resource muting |
Apple |
| R4-2504483 |
Cross Link Interference (CLI) handling impact on MPR for SBFD operation |
Qualcomm Incorporated |
| 7.23.2 |
BS RF requirements |
|
| R4-2504300 |
Deployment scenarios for FR1 SBFD macro BS |
Huawei, HiSilicon, Samsung, Qualcomm, Verizon, Vodafone, China Telecom, China Unicom |
| 7.23.2.1 |
Potentially new requirements for SBFD operation for FR1 and FR2-1 |
|
| R4-2503286 |
Discussion on Potentially new requirements for SBFD operation |
Tejas Network Limited |
| R4-2503404 |
Discussion on new RF requirement for SBFD |
CMCC |
| R4-2503469 |
Discussion on potentially new requirements for SBFD operation |
CATT |
| R4-2504008 |
New SBFD BS RF requirements |
Ericsson |
| R4-2504092 |
On potentially new requirements for SBFD |
Huawei, HiSilicon |
| R4-2504194 |
On potentially new BS RF requirements for SBFD operation |
Nokia |
| R4-2504219 |
On the new requirements for SBFD operation for FR1 and FR2-1 |
Samsung |
| R4-2504341 |
Views on new BS RF requirements for SBFD |
Qualcomm Germany |
| R4-2504369 |
Discussion on potentially new requirements for SBFD operation |
ZTE Corporation, Sanechips |
| 7.23.2.2 |
Modification of existing Tx requirements for FR1 and FR2-1 |
|
| R4-2503287 |
Discussion on existing Tx requirements for SBFD operation |
Tejas Network Limited |
| R4-2503403 |
Discussion on existing Tx requirements for SBFD |
CMCC |
| R4-2503467 |
Discussion on modification of existing Tx requirements for SBFD operation |
CATT |
| R4-2504009 |
Impact on SBFD BS RF TX requirements |
Ericsson |
| R4-2504195 |
On existing BS RF TX requirements for SBFD operation |
Nokia |
| R4-2504220 |
On the modification of existing TX requirements for SBFD-capable BS |
Samsung |
| R4-2504301 |
On modification of existing TX RF requirements for SBFD |
Huawei, HiSilicon |
| R4-2504340 |
Views on existing BS RF requirements for SBFD |
Qualcomm Germany |
| R4-2504370 |
Discussion on modification of existing Tx requirements for FR1 and FR2-1 for SBFD BS |
ZTE Corporation, Sanechips |
| 7.23.2.3 |
Modification of existing Rx requirements for FR1 and FR2-1 |
|
| R4-2503299 |
Views on modification of existing Rx requirements for SBFD |
Tejas Network Limited |
| R4-2503402 |
Discussion on existing Rx requirements for SBFD |
CMCC |
| R4-2503468 |
Discussion on modification of existing Rx requirements for SBFD operation |
CATT |
| R4-2504010 |
Impact on SBFD BS RF RX requirements |
Ericsson |
| R4-2504196 |
On existing BS RF RX requirements for SBFD operation |
Nokia |
| R4-2504221 |
On the modification of existing RX requirements for SBFD-capable BS |
Samsung |
| R4-2504302 |
On modification of existing RX RF requirements for SBFD |
Huawei, HiSilicon |
| R4-2504371 |
Discussion on modification of existing Rx requirements for FR1 and FR2-1 for SBFD BS |
ZTE Corporation, Sanechips |
| 7.23.3.1 |
RRM requirements for UE-to-UE CLI handling |
|
| R4-2503290 |
On RRM requirements for UE-to-UE CLI handling |
vivo |
| R4-2503341 |
On RRM requirements for UE-to-UE CLI handling |
OPPO |
| R4-2503414 |
Discussion on UE to UE CLI handling |
CATT |
| R4-2503500 |
RRM requirements for UE-to-UE CLI handling |
Nokia, Nokia Shanghai Bell |
| R4-2503502 |
Simulation result for L1-CLI-SRS-RSRP measurement |
Nokia, Nokia Shanghai Bell |
| R4-2503578 |
Discussion on RRM impacts of UE-to-UE CLI handling |
LG Electronics Inc. |
| R4-2503667 |
Views on L1 CLI measurement requirements |
Samsung |
| R4-2503750 |
Discussion for RRM requirements for SBFD UE to UE CLI handling |
Ericsson |
| R4-2503762 |
Discussion on RRM requirements for UE-to-UE CLI handling |
CMCC |
| R4-2503901 |
Discussion on UE CLI measurement for SBFD |
Huawei, HiSilicon |
| R4-2503902 |
Additional simulation results for UE CLI measurement |
Huawei, HiSilicon |
| R4-2503915 |
Discussion on RRM requirements for UE-to-UE CLI handling for evolution of NR duplex operation |
China Telecom |
| R4-2504250 |
Discussion on UE-to-UE CLI of R19 SBFD |
ZTE Corporation, Sanechips |
| R4-2504454 |
On UE RRM requirements for UE-to-UE CLI handling |
Apple |
| R4-2504479 |
Discussion on SBFD UE-to-UE CLI |
MediaTek inc. |
| R4-2504608 |
RRM requirements for UE-to-UE CLI handling |
Qualcomm Incorporated |
| 7.23.3.2 |
RRM impacts for SBFD operation |
|
| R4-2503291 |
Further consideration on RRM impacts for SBFD operation |
vivo |
| R4-2503342 |
On RRM impacts for SBFD operation |
OPPO |
| R4-2503415 |
Discussion on impacts of SBFD on RRM requirements |
CATT |
| R4-2503501 |
RRM requirements for SBFD operation |
Nokia, Nokia Shanghai Bell |
| R4-2503579 |
Discussion on RRM impacts of SBFD operation |
LG Electronics Inc. |
| R4-2503668 |
Views on RRM requirements for Rel-19 SBFD operation |
Samsung |
| R4-2503751 |
Discussion on RRM impacts for SBFD operations |
Ericsson |
| R4-2503761 |
Discussion on RRM impacts for SBFD operation |
CMCC |
| R4-2503903 |
Discussion on RRM impacts for SBFD operation |
Huawei, HiSilicon |
| R4-2503916 |
Discussion on RRM impacts for SBFD operation for evolution of NR duplex operation |
China Telecom |
| R4-2504251 |
Discussion on other RRM impacts of R19 SBFD |
ZTE Corporation, Sanechips |
| R4-2504480 |
Discussion on SBFD Operation |
MediaTek inc. |
| R4-2504607 |
RRM requirements for SBFD operation |
Qualcomm Incorporated |
| 7.23.4 |
Moderator summary and conclusions |
|
| R4-2503623 |
Topic summary for [114bis][213] NR_duplex_evo |
Moderator (Huawei) |
| R4-2504631 |
Topic summary for [114bis][306] NR_duplex_evo_General |
Moderator (Samsung) |
| R4-2504632 |
Topic summary for [114bis][307] NR_duplex_evo_BSRF |
Moderator (Huawei) |
| R4-2504745 |
Ad-hoc meeting minutes for [114bis][306] NR_duplex_evo_General |
Samsung |
| R4-2504746 |
Way Forward for [114bis][306] NR_duplex_evo_General |
Samsung |
| R4-2504747 |
Ad-hoc meeting minutes for [114bis][307] NR_duplex_evo_BSRF |
Huawei |
| R4-2504748 |
Way Forward for [114bis][307] NR_duplex_evo_BSRF |
Huawei |
| R4-2504751 |
Way Forward for [114bis][306] NR_duplex_evo_General |
Samsung |
| R4-2504752 |
Way Forward for [114bis][307] NR_duplex_evo_BSRF |
Huawei |
| R4-2504767 |
LS on the transient period for SBFD operation |
Samsung |
| R4-2504904 |
WF on RRM requirements for NR_duplex_evo |
Huawei |
| R4-2504919 |
Ad-hoc minutes for NR_duplex_evo |
Samsung |
| R4-2504948 |
Reply LS on L1 based UE-to-UE CLI measurement and reporting |
Huawei |
| R4-2504949 |
Updated summary of simulation results for L1-SRS-RSRP |
Huawei |
| R4-2504950 |
Ad-hoc #2 minutes for NR_duplex_evo |
Samsung |
| R4-2504964 |
Reply LS on L1 based UE-to-UE CLI measurement and reporting |
Huawei |
| 7.24.1 |
General aspects |
|
| R4-2503216 |
A-IoT general aspects |
Huawei, HiSilicon |
| R4-2503314 |
Discussion on AIoT system parameters |
Xiaomi |
| R4-2503392 |
Discussion on A-IoT general requirements |
CMCC |
| R4-2503472 |
Discussion on system parameters for A-IoT |
CATT |
| R4-2503673 |
Discussion on system parameters for ambient IoT |
Spreadtrum,UNISOC |
| R4-2503813 |
Discussion on the systeme parameter of AIoT |
vivo |
| R4-2503932 |
(new) TS 38.191 Ambient IoT device radio transmission and reception |
CMCC |
| R4-2504069 |
3GPP_TS 38.194 skeleton |
Huawei, HiSilicon |
| R4-2504096 |
3GPP_TS 38.194 skeleton |
Huawei, HiSilicon |
| R4-2504207 |
on system parameter |
OPPO |
| R4-2504352 |
Discussions on General aspect for A-IoT |
ZTE Corporation, Sanechips |
| R4-2504399 |
A-IoT general overview |
Ericsson |
| R4-2505227 |
(new) TS 38.191 Ambient IoT device radio transmission and reception |
CMCC |
| R4-2505228 |
3GPP_TS 38.194 skeleton |
Huawei, HiSilicon |
| 7.24.2.1 |
RF requirements for Type 1-C Ambient-IoT BS |
|
| R4-2503217 |
RF requirements for A-IoT BS |
Huawei, HiSilicon |
| R4-2503315 |
Initial D2R LLS simulation result |
Xiaomi |
| R4-2503390 |
Discussion on A-IoT BS RF requirements |
CMCC |
| R4-2503470 |
Discussion on A-IoT BS requirements |
CATT |
| R4-2503560 |
Relevance of phase noise and LLS for SNR for REFSENS |
Qualcomm Incorporated |
| R4-2503814 |
Discussion on the RF requirement for AIoT BS |
vivo |
| R4-2504353 |
Discussions on RF requirements for A-IoT BS |
ZTE Corporation, Sanechips |
| R4-2504398 |
A-IoT BS RF impact overview |
Ericsson |
| 7.24.2.2 |
RF requirements for device 1 |
|
| R4-2503316 |
Discussion on AIoT device 1 RF requirement |
Xiaomi |
| R4-2503391 |
Discussion on A-IoT device RF requirements |
CMCC |
| R4-2503438 |
Discussion on Ambient IoT device 1 RF requirements |
CATT |
| R4-2503559 |
Ambient IoT device backscattering and SFO error |
Qualcomm Incorporated |
| R4-2503671 |
Discussion on RF requirements for ambient IoT device 1 |
Spreadtrum,UNISOC |
| R4-2503815 |
Discussion on the RF requirement for device 1 |
vivo |
| R4-2504063 |
RF requirements of ambient IoT device 1 |
Sony |
| R4-2504206 |
on RF requirements for device 1 |
OPPO |
| R4-2504354 |
Discussion on RF requirement of Ambient IoT device |
ZTE Corporation, Sanechips |
| R4-2504377 |
Discussion on RF requirement for A-IoT device 1 |
LG Electronics UK |
| R4-2504400 |
A-IoT device requirement overview |
Ericsson |
| R4-2504516 |
Discussion on RF requirement for A-IoT device 1 |
LG Electronics UK |
| R4-2504557 |
On the RF requirements for Ambient IoT Device |
Huawei, HiSilicon |
| 7.24.2.3 |
RF requirements for CW |
|
| R4-2503317 |
Discussion on AIoT CW requirements |
Xiaomi |
| R4-2503389 |
Discussion on A-IoT CW RF requirements |
CMCC |
| R4-2503471 |
Discussion on RF requirements for CW for D1T1 |
CATT |
| R4-2503672 |
Discussion on RF requirements for CW |
Spreadtrum,UNISOC |
| R4-2503816 |
Discussion on the RF requirement for CW |
vivo |
| R4-2504205 |
on RF requirements for CW |
OPPO |
| R4-2504303 |
RF requirements for CW |
Huawei, HiSilicon |
| R4-2504355 |
Discussion on RF requirement for CW node |
ZTE Corporation, Sanechips |
| R4-2504401 |
CW node RF impact overview |
Ericsson |
| R4-2504409 |
Discussion on RF requirement for CW |
LG Electronics UK |
| R4-2504517 |
Discussion on RF requirement for CW |
LG Electronics UK |
| 7.24.3 |
RRM core requirements |
|
| R4-2503292 |
Initial discussion on RRM impacts for R19 A-IoT device |
vivo |
| R4-2503422 |
Discussion on the impacts of A-IoT on RRM requirements |
CATT |
| R4-2503778 |
Discussion on RRM requirements for A-IoT |
CMCC |
| R4-2503788 |
Discussions on RRM requirements for A-IoT |
NTT DOCOMO, INC. |
| R4-2503791 |
Discussion on RRM requirements for Ambient-IoT |
ZTECorporation,Sanechips |
| R4-2503873 |
Discussion on RRM impacts for R19 A-IoT device |
Huawei, HiSilicon |
| R4-2503954 |
Discussion on RRM requirements for ambient IoT device 1 |
Spreadtrum,UNISOC |
| R4-2504108 |
Initial discussion on RRM requirements for Ambient-IoT |
Ericsson |
| 7.24.4 |
OTA test method for A-IoT device 1 |
|
| R4-2503138 |
Discussion on OTA testing for A-IoT device 1 |
Ericsson-LG Co., LTD |
| R4-2503393 |
Discussion on A-IoT OTA requirements |
CMCC |
| R4-2503494 |
on OTA tests for ambient IoT devices |
Huawei, HiSilicon |
| R4-2503817 |
Discussion on the OTA test method for device |
vivo |
| R4-2504056 |
Views on Ambient IoT Testability |
Qualcomm Incorporated |
| R4-2504064 |
Consideration on the OTA test of ambient IoT device 1 |
Sony |
| R4-2504151 |
Discussion on OTA test method for A-IoT device |
CAICT |
| R4-2504204 |
on OTA test aspect |
OPPO |
| 7.24.5 |
Moderator summary and conclusions |
|
| R4-2503624 |
Topic summary for [114bis][214] Ambient_IoT_Solutions |
Moderator (CMCC) |
| R4-2504687 |
Topic summary for [114bis][129] A-IoT_device |
Moderator(CMCC) |
| R4-2504688 |
Topic summary for [114bis][130] A-IoT_BSCW |
Moderator(Huawei) |
| R4-2505096 |
WF on A-IoT device requirements |
CMCC |
| R4-2505097 |
WF on A-IoT BS and CW requirements |
Huawei |
| R4-2505230 |
WF on A-IoT device requirements |
CMCC |
| 7.25.1 |
General aspects |
|
| R4-2504225 |
Discussion on OD-SSB general part in Rel-19 NES |
Ericsson |
| 7.25.2.1 |
On-demand SSB SCell operation |
|
| R4-2503124 |
Views on on-demand SSB SCell operation |
Qualcomm Technologies Ireland |
| R4-2503130 |
Discussion on RRM requirements for OD-SSB for network energy saving |
MediaTek inc. |
| R4-2503293 |
Discussion on RRM requirements for on-demand SSB SCell operation in R19 NES |
vivo |
| R4-2503327 |
Discussion on OD-SSB requirements |
Xiaomi |
| R4-2503343 |
On RRM requirements of on-demand SSB SCell operation |
OPPO |
| R4-2503380 |
Discussion on RRM requirement of OD-SSB for NES enhancement |
CMCC |
| R4-2503429 |
Discussion on RRM requirements for on-demand SSB SCell operation |
CATT |
| R4-2503499 |
RRM requirements for OD-SSB SCell operation |
Nokia, Nokia Shanghai Bell |
| R4-2503569 |
Discussion on on-demand SSB SCell operation |
Apple |
| R4-2503591 |
Discussion on RRM requirements of on-demand SSB Scell operation for Rel-19 NES |
LG Electronics |
| R4-2503866 |
Discussion on RRM impact for Rel-19 NES OD-SSB |
Huawei, HiSilicon |
| R4-2503917 |
Discussion on On-demand SSB SCell operation for enhancements of network energy savings for NR |
China Telecom |
| R4-2504019 |
Discussion on RRM requirements for On-demand SSB SCell operations |
Intel Corporation |
| R4-2504226 |
Discussion on OD-SSB in Rel-19 NES |
Ericsson |
| R4-2504246 |
Discussion on On-demand SSB SCell operation of R19 NES |
ZTE Corporation, Sanechips |
| R4-2504289 |
Discussion on RRM requirements for NES OD-SSB |
Samsung |
| 7.25.2.2 |
Adaptation of common signal/channel transmission |
|
| R4-2503125 |
About RRM requirements for adaptation of common signal/channel transmission |
Qualcomm Technologies Ireland |
| R4-2503131 |
Discussion on RRM requirements for adaptation of common signal/channel transmission |
MediaTek inc. |
| R4-2503294 |
On RRM requirements for common signal or channel adaptation in R19 NES |
vivo |
| R4-2503328 |
Discussion on RRM requirements for adaptation of common signal/channel in NES |
Xiaomi |
| R4-2503344 |
On RRM requirements of SSB adaptation |
OPPO |
| R4-2503381 |
Discussion on RRM requirement of signal adapatation for NES enhancement |
CMCC |
| R4-2503430 |
Discussion on RRM requirements for adaptation of common signalchannel transmission |
CATT |
| R4-2503570 |
Discussion on adaptation of common signal/channel transmission |
Apple |
| R4-2503594 |
Discussion on RRM requirements of SSB adaptation for Rel-19 NES |
LG Electronics |
| R4-2503867 |
Discussion on RRM impact for Rel-19 NES on adaptation |
Huawei, HiSilicon |
| R4-2503918 |
Discussion on adaptation of common signal/channel transmission for enhancements of network energy savings for NR |
China Telecom |
| R4-2504227 |
Discussion on RS and channel adaptation in Rel-19 NES |
Ericsson |
| R4-2504247 |
Discussion on adaptation of common signal and channel of R19 NES |
ZTE Corporation, Sanechips |
| R4-2504290 |
General discussion on the NES common signal adaptation |
Samsung |
| R4-2504506 |
RRM requirements for SSB adaptation |
Nokia, Nokia Shanghai Bell |
| 7.25.2.3 |
On-demand SIB1 |
|
| R4-2503126 |
On RRM requirements for on-demand SIB1 |
Qualcomm Technologies Ireland |
| R4-2503295 |
Discussion on RRM requirement impacts from on-demand SIB1 in R19 NES |
vivo |
| R4-2503345 |
On RRM requirement for on-demand SIB1 |
OPPO |
| R4-2503382 |
Discussion on RRM requirement of OD-SIB1 for NES enhancement |
CMCC |
| R4-2503431 |
Discussion on RRM requirements for On-demand SIB1 |
CATT |
| R4-2503571 |
Discussion on on-demand SIB1 |
Apple |
| R4-2503596 |
Discussion on RRM requirements of on-demand SIB1 for Rel-19 NES |
LG Electronics |
| R4-2503868 |
Discussion on RRM impact for Rel-19 OD-SIB1 |
Huawei, HiSilicon |
| R4-2504228 |
Discussion on OD-SIB1 in Rel-19 NES |
Ericsson |
| R4-2504507 |
RRM requirements for On-demand-SIB1 |
Nokia, Nokia Shanghai Bell |
| 7.25.3 |
Moderator summary and conclusions |
|
| R4-2503625 |
Topic summary for [114bis][215] Netw_Energy_NR_enh_Part1 |
Moderator (Ericsson) |
| R4-2503626 |
Topic summary for [114bis][216] Netw_Energy_NR_enh_Part2 |
Moderator (Huawei) |
| R4-2504905 |
WF on RRM requirements for Ambient_IoT_Solutions |
CMCC |
| R4-2504906 |
WF on RRM requirements for Netw_Energy_NR_enh_Part1 |
Ericsson |
| R4-2504907 |
WF on RRM requirements for Netw_Energy_NR_enh_Part2 |
Huawei |
| R4-2504920 |
Ad-hoc minutes for Netw_Energy_NR_enh |
Ercisson |
| 7.26.1 |
General aspects and RF TR (for email approval) |
|
| R4-2503804 |
Further consideration on general aspects of LP-WUS |
Huawei, HiSilicon |
| R4-2503830 |
TR 38.774 v0.3.0 |
vivo |
| R4-2503831 |
Draft Big CR for LP-WUS UE RF requirements in Rel-19 |
vivo |
| R4-2504393 |
On general issues for WUR |
Ericsson |
| R4-2504417 |
TP for TR 38.774 on LP-WUS |
Nokia |
| R4-2505150 |
TP for TR 38.774 on LP-WUS |
Nokia |
| R4-2505236 |
TP for TR 38.774 on LP-WUS |
Nokia |
| 7.26.2 |
UE RF requirements for LP-WUS/WUR |
|
| R4-2504065 |
views on requirements of the low-power wake-up receiver |
Sony |
| 7.26.2.1 |
System parameters |
|
| R4-2503400 |
Discussion on LP-WUS UE system parameters requirements |
CMCC |
| R4-2503483 |
TP to TR 38.774 on Clause 5 (System parameters) |
CATT |
| R4-2503832 |
TP to TR 38.774 on LP-WUS |
vivo |
| R4-2504394 |
On system parameter for WUR |
Ericsson |
| R4-2504413 |
System parameters for LP-WUR |
Nokia |
| R4-2505148 |
TP to TR 38.774 on Clause 5 (System parameters) |
CATT, Ericsson |
| R4-2505149 |
TP to TR 38.774 on LP-WUS |
vivo, Ericsson |
| 7.26.2.2 |
Rx requirements of REFSENS, ASCS and ACS |
|
| R4-2503170 |
On UE RF requirements for the LPWUR |
Qualcomm Incorporated |
| R4-2503191 |
On LP-WUR Rx requirements |
Apple |
| R4-2503399 |
Discussion on LP-WUS UE RF Rx requirements of REFSENS, ASCS and ACS |
CMCC |
| R4-2503484 |
Further discussion on REFSENS for LP-WUS |
CATT |
| R4-2503638 |
Discussion on REFSENS, ASCS, ACS for LP-WUR |
ZTE Corporation, Sanechips |
| R4-2503648 |
Discussion on UE RF requirements for FR2 LP-WUR |
Samsung |
| R4-2503805 |
Further consideration on UE REFSENS, ACS requirements for Rel-19 LP-WUS |
Huawei, HiSilicon |
| R4-2503833 |
Updates on LP-WUS REFSENS, ASCS and ACS |
vivo |
| R4-2504397 |
WUR RF requirement REFSESN ACS ASCS |
Ericsson |
| R4-2504414 |
Fundamental RX requirements for LP-WUR |
Nokia |
| 7.26.2.3 |
Rx requirements of IBB, OBB, intermodulation, spurious emissions and others |
|
| R4-2503401 |
Discussion on LP-WUS UE RF Rx requirements of IBB, OBB, intermodulation, spurious emissions and others |
CMCC |
| R4-2503485 |
Further discussion on other RF requirements for LP-WUS |
CATT |
| R4-2503639 |
Discussion on receiver characteristics for LP-WUR |
ZTE Corporation, Sanechips |
| R4-2503806 |
Further consideration on UE RF other Rx requirements for Rel-19 LP-WUS |
Huawei, HiSilicon |
| R4-2503834 |
draft CR to 38.101-1 on LP-WUS UE RF |
vivo |
| R4-2504396 |
WUR RF requirement other than REFSENS |
Ericsson |
| R4-2504415 |
Other RX requirements for LP-WUR |
Nokia |
| 7.26.2.4 |
Testability for UE RF requirements |
|
| R4-2503171 |
On test method for UE RF requirements for the LPWUR |
Qualcomm Incorporated |
| R4-2503486 |
Further discussion on Testability for UE RF requirements for LP-WUS |
CATT |
| R4-2503640 |
Discussion on testability of LP-WUR |
ZTE Corporation, Sanechips |
| R4-2503649 |
Discussion on testability for LP-WUR |
Samsung |
| R4-2503807 |
Further consideration on UE RF testability issues for Rel-19 LP-WUS |
Huawei, HiSilicon |
| R4-2504395 |
On WUR RF requirement testability |
Ericsson |
| R4-2504416 |
Testability aspects of LP-WUR |
Nokia |
| 7.26.3 |
BS RF requirements for LP-WUS/WUR |
|
| R4-2503168 |
BS RF requirements for low-power wake-up signal for NR |
Nokia |
| R4-2503398 |
Discussion on LP-WUS BS RF requirements |
CMCC |
| R4-2503487 |
Further discussion on BS RF requirements for LP-WUS |
CATT |
| R4-2503488 |
draftCR to TS 38.141-1 on declaration of support for LP-WUS |
CATT |
| R4-2503489 |
draftCR to TS 38.141-2 on declaration of support for LP-WUS |
CATT |
| R4-2503636 |
Discussion on BS RF requirements for LP-WUS/WUR |
ZTE Corporation, Sanechips |
| R4-2503637 |
TP to TR 38.774 on LP-WUS power boosting (Clause 7.2.2) |
ZTE Corporation, Sanechips |
| R4-2503808 |
Further consideration on BS RF for Rel-19 LP-WUS |
Huawei, HiSilicon |
| R4-2504392 |
TP to TR38.774: BS RF requirement overview for LP-WUS |
Ericsson |
| R4-2504743 |
TP to TR 38.774 on LP-WUS power boosting (Clause 7.2.2) |
ZTE Corporation, Sanechips, Ericsson, Huawei, Nokia and CATT |
| 7.26.4.1 |
Simulation assumptions and results |
|
| R4-2503296 |
Further discussion on simulation assumptions for LP-WUR |
vivo |
| R4-2503297 |
Simulation results for LP-WUR |
vivo |
| R4-2503301 |
Discussion on simulation assumptions and results for LP-WUS/WUR |
Xiaomi |
| R4-2503354 |
Simulation assumption and results for LP-WUSWUR |
OPPO |
| R4-2503383 |
Simulation assumption and results for LP-WUR |
CMCC |
| R4-2503527 |
Discussion of Simulation Assumptions for LP-WUR RRM Requirements |
Apple |
| R4-2503528 |
Summary of Simulation Results for LP-WUR RRM Requirements |
Apple |
| R4-2503580 |
Discussion on simulation assumptions and results for LP-WUS/WUR |
LG Electronics Inc. |
| R4-2503796 |
Discussion on OOK based LP-WUR simulation |
ZTECorporation,Sanechips |
| R4-2503899 |
Simulation assumption and additional simulation results for LP-WUR measurement |
Huawei, HiSilicon |
| R4-2504223 |
Simulation assumption on LP-WUS RRM measurement |
Ericsson |
| R4-2504224 |
Simulation on LP-WUS RRM measurement |
Ericsson |
| R4-2504466 |
Simulation results for RRM LP-SS simulation campaign |
Nokia |
| R4-2504467 |
Discussion on LP-WUS RRM Simulations |
Nokia |
| R4-2504598 |
Simulation assumptions for R19 LP-WUS |
MediaTek inc. |
| 7.26.4.2 |
RRM core requirements |
|
| R4-2503298 |
Consideration on remaining RRM issues for LP-WUR |
vivo |
| R4-2503302 |
Discussion on RRM core requirements for LP-WUS/WUR |
Xiaomi |
| R4-2503355 |
Discussion on RRM requirements for LP-WUSWUR |
OPPO |
| R4-2503384 |
Discussion on RRM impact of LP-WUR |
CMCC |
| R4-2503432 |
Discussion on RRM requirements for LP-WUS/WUR |
CATT |
| R4-2503533 |
On RRM core requirements for LP-WUR |
Apple |
| R4-2503534 |
Reply LS on the wake-up delay for LP-WUS operation in IDLE/INACTIVE mode |
Apple |
| R4-2503581 |
Discussion on RRM core requirements for LP-WUS/WUR |
LG Electronics Inc. |
| R4-2503792 |
Discussion on LP-WUS for core part |
ZTECorporation,Sanechips |
| R4-2503803 |
Draft reply LS to RAN1 on wake-up delay for LP-WUS operation in IDLE/INACTIVE mode |
ZTECorporation,Sanechips |
| R4-2503900 |
Discussion on RRM requirements for LP-WUR |
Huawei, HiSilicon |
| R4-2503919 |
Discussion on RRM core requirements for LP-WUS/WUR |
China Telecom |
| R4-2504222 |
Discussion on LP-WUS RRM requirement |
Ericsson |
| R4-2504468 |
Discussion on LP-WUS core requirements |
Nokia |
| R4-2504599 |
Discussion on the RRM core requirements for LP-WUS |
MediaTek inc. |
| R4-2504605 |
RRM requirements for LP-WUR |
Qualcomm Incorporated |
| 7.26.5 |
Moderator summary and conclusions |
|
| R4-2503627 |
Topic summary for [114bis][217] NR_LPWUS |
Moderator (vivo) |
| R4-2504633 |
Topic summary for [114bis][308] NR_LPWUS |
Moderator (Huawei) |
| R4-2504689 |
Topic summary for [114bis][131] NR_LPWUS_UERF |
Moderator(Vivo) |
| R4-2504742 |
Ad-hoc meeting minutes for [114bis][308] NR_LPWUS |
Huawei |
| R4-2504744 |
Way Forward for [114bis][308] NR_LPWU |
Huawei |
| R4-2504908 |
WF on RRM requirements for NR_LPWUS |
vivo |
| R4-2504921 |
Ad-hoc minutes for NR_LPWUS |
vivo |
| R4-2505104 |
WF on UE RF requirements for LP-WUS |
Vivo |
| R4-2505234 |
WF on UE RF requirements for LP-WUS |
Vivo |
| 7.27.2.1 |
Event triggered L1 measurement reporting |
|
| R4-2503310 |
Discussion on event triggered L1 measurement reporting for mobility |
Xiaomi |
| R4-2503346 |
On event triggered L1 measurement reporting |
OPPO |
| R4-2503433 |
Discussion on Event triggered L1 measurement reporting for Rel-19 LTM enhancements |
CATT |
| R4-2503572 |
Discussion on event triggered L1 measurement reporting |
Apple |
| R4-2503603 |
Discussion on event triggered L1 report for LTM |
MediaTek Inc. |
| R4-2503757 |
Discussion on event triggered L1 measurement reporting |
CMCC |
| R4-2503854 |
Discussion on event triggered L1 measurement reporting |
ZTE Corporation, Sanechips |
| R4-2503883 |
Discussion on Event triggered L1 measurement reporting |
Huawei, HiSilicon |
| R4-2503936 |
Discussion on Event triggered L1 measurement reporting |
Ericsson |
| R4-2503987 |
RRM Core requirements on event triggered L1 measurement reporting |
China Telecom |
| R4-2504030 |
On RRM requirements for LTM event-triggered L1-RSRP reporting |
vivo |
| R4-2504071 |
On event-triggered L1 reporting for LTM |
Nokia |
| R4-2504072 |
DraftCR for LTM event-triggered L1 requirements |
Nokia |
| 7.27.2.2 |
CSI-RS based L1 measurement |
|
| R4-2503311 |
Discussion on CSI-RS based L1 for mobility |
Xiaomi |
| R4-2503347 |
On CSI-RS based L1 measurement |
OPPO |
| R4-2503434 |
Discussion on CSI-RS based L1 measurement for Rel-19 LTM enhancements |
CATT |
| R4-2503585 |
CSI-RS based L1-RSRP measurement |
Apple |
| R4-2503604 |
Discussion on CSI-RS L1 measurement for LTM |
MediaTek Inc. |
| R4-2503758 |
Discussion on CSI-RS based L1 measurement |
CMCC |
| R4-2503855 |
Discussion on CSI-RS based L1-RSRP measurement |
ZTE Corporation, Sanechips |
| R4-2503884 |
Discussion on CSI-RS based L1 measurement |
Huawei, HiSilicon |
| R4-2503937 |
Discussion on CSI-RS based L1 measurement |
Ericsson |
| R4-2503988 |
RRM Core requirements on CSI-RS based L1 measurement |
China Telecom |
| R4-2504031 |
On RRM requirements for LTM CSI-RS based L1 measurement |
vivo |
| R4-2504470 |
Discussion on CSI-RS based L1 measurements |
Nokia |
| R4-2504527 |
CSI-RS based L1 measurement for LTM |
Qualcomm Incorporated |
| 7.27.2.3 |
Conditional Intra-CU LTM |
|
| R4-2503303 |
Discussion on Conditional Intra-CU LTM for NR mobility enhancements Phase 4 |
Xiaomi |
| R4-2503435 |
Discussion on conditional Intra-CU LTM for Rel-19 mobility enhancements |
CATT |
| R4-2503573 |
Discussion on conditional Intra-CU LTM |
Apple |
| R4-2503605 |
Discussion on Conditional LTM |
MediaTek Inc. |
| R4-2503752 |
Discussion on intra-CU conditional LTM |
Ericsson |
| R4-2503759 |
Discussion on conditional intra-CU LTM |
CMCC |
| R4-2503856 |
Discussion on Conditional Intra-CU LTM |
ZTE Corporation, Sanechips |
| R4-2503885 |
Discussion on conditional Intra-CU LTM |
Huawei, HiSilicon |
| R4-2503989 |
RRM Core requirements on conditional Intra-CU LTM |
China Telecom |
| R4-2504052 |
Further discussion on Conditional Intra-CU LTM |
vivo |
| R4-2504202 |
On CLTM RRM requirements |
Nokia |
| R4-2504528 |
Conditional LTM |
Qualcomm Incorporated |
| 7.27.3 |
Moderator summary and conclusions |
|
| R4-2503628 |
Topic summary for [114bis][218] NR_Mob_Ph4_Part1 |
Moderator (Apple) |
| R4-2503629 |
Topic summary for [114bis][219] NR_Mob_Ph4_Part2 |
Moderator (China Telecom) |
| R4-2504909 |
WF on RRM requirements for NR_Mob_Ph4_Part1 |
Apple |
| R4-2504910 |
WF on RRM requirements for NR_Mob_Ph4_Part2 |
China Telecom |
| R4-2504965 |
WF on RRM requirements for NR_Mob_Ph4_Part1 |
Apple |
| 7.28.1 |
General aspects |
|
| R4-2503921 |
draftCR38133 Inter-frequency measurement requirements with XR |
Ericsson |
| R4-2504504 |
Collection of XR_Ph3 agreements for information |
Nokia |
| 7.28.2 |
RRM core requirements |
|
| R4-2503236 |
NR_XR_Ph3 remaining issues |
InterDigital, Inc. |
| R4-2503574 |
Discussion of RRM impact of XR for NR Phase 3 |
Apple |
| R4-2503575 |
Inter-RAT measurements E-UTRAN TDD measurements |
Apple |
| R4-2503760 |
Discussion on XR (eXtended Reality) for NR Phase 3 |
CMCC |
| R4-2503870 |
Discussion on RRM requirements for Rel-19 XR |
Huawei, HiSilicon |
| R4-2503922 |
On RRM requirements for XR |
Ericsson |
| R4-2504027 |
Further discussion on RRM requirements for XR |
vivo |
| R4-2504029 |
Draft CR on NR inter-frequency L1 measurement for XR |
vivo |
| R4-2504252 |
Discussion on RRM aspects of R19 XR |
ZTE Corporation, Sanechips |
| R4-2504257 |
Draft CR on measurement gap skipping in intra-frequency measurement with gaps for R19 XR |
ZTE Corporation, Sanechips |
| R4-2504291 |
General discussion on XR requirement |
Samsung |
| R4-2504481 |
Discussion on RRM requirements for XR |
MediaTek inc. |
| R4-2504505 |
Analysis of skip ratio on XR capacity and mobility performance |
Nokia |
| R4-2504508 |
Discussion on XR ph3 RRM requirements |
Nokia |
| R4-2504509 |
Draft CR38.133 Introduction of measurement gap cancellation |
Nokia |
| R4-2504606 |
RRM requirements for XR enhancements |
Qualcomm Incorporated |
| R4-2504622 |
Discussion on RRM Requirements for XR |
Meta |
| 7.28.3 |
Moderator summary and conclusions |
|
| R4-2503630 |
Topic summary for [114bis][220] NR_XR_Ph3 |
Moderator (Nokia) |
| R4-2504911 |
WF on RRM requirements for NR_XR_Ph3 |
Nokia |
| R4-2504922 |
Ad-hoc minutes for NR_Mob_Ph4 |
Apple |
| R4-2504923 |
Ad-hoc minutes for NR_XR_Ph3 |
Nokia |
| R4-2504968 |
Reply LS on UE assistance information |
Nokia |
| R4-2504972 |
Reply LS on UE assistance information |
Nokia |
| 7.29.1 |
General aspects |
|
| R4-2503451 |
DraftCR for TS 38.181, Introduction on SAN diagram for SAN supporting regenerative payload |
CATT |
| R4-2503713 |
Draft CR to TS 38.108: Correction of Regenerative Payload Figures |
NEC Europe Ltd, THALES |
| R4-2503824 |
Discussion on simultaneous operation between GNSS and UL transmission in NR NTN |
vivo |
| R4-2503825 |
Draft reply LS on simultaneous operation between GNSS and UL transmission in NR NTN |
vivo |
| R4-2504406 |
LS reply on IDC of GNSS |
Ericsson |
| R4-2504706 |
Draft CR to TS 38.108: Correction of Regenerative Payload Figures |
NEC Europe Ltd, THALES, HUAWEI, CATT, Ericsson |
| R4-2504707 |
DraftCR for TS 38.181, Introduction on SAN diagram for SAN supporting regenerative payload |
CATT, NEC, Thales, HUAWEI, Ericsson |
| 7.29.2.1 |
RedCap UE RF requirements |
|
| R4-2503444 |
Discussion on RF requirements for NTN RedCap UE |
CATT |
| R4-2503693 |
Discussion on the simultaneous operation between GNSS and NR NTN |
Huawei, HiSilicon |
| R4-2503732 |
Discussion on NTN (e)Redcap UE RF requirements |
Spreadtrum,UNISOC |
| R4-2504403 |
RedCap UE RF impact on HD-FDD |
Ericsson |
| R4-2504418 |
RedCap NTN UEs |
Nokia |
| R4-2504428 |
Discussion on Rel-19 NR-NTN RedCap UE RF requirements |
MediaTek (Hefei) Inc. |
| R4-2504550 |
On simultaneous operation between GNSS and NR NTN |
Qualcomm Inc. |
| R4-2504551 |
Draft CR to TS 38.101-5: Introduction of RedCap and eRedCap |
Qualcomm Inc. |
| 7.29.2.2 |
Other requirements |
|
| R4-2504066 |
GNSS simultaneously operation with NR NTN |
Sony |
| R4-2504404 |
Other NTN UE RF impact |
Ericsson |
| R4-2504552 |
NR NTN UL Capacity Enhancements |
Qualcomm Inc. |
| 7.29.3 |
SAN RF requirements |
|
| R4-2503445 |
Discussion on SAN diagram for NTN SAN |
CATT |
| R4-2503450 |
DraftCR for TS 38.108, Introduction on SAN diagram for SAN supporting regenerative payload |
CATT |
| 7.29.4.1 |
(e)RedCap RRM requirements |
|
| R4-2503304 |
Discussion on (e)RedCap RRM requirements in NTN for NR Phase 3 |
Xiaomi |
| R4-2503348 |
Discussion on (e)RedCap RRM requirements of R19 NR NTN |
OPPO |
| R4-2503385 |
Discussion on the RRM requirement for Redcap over NTN |
CMCC |
| R4-2503436 |
Discussion on (e)RedCap RRM requirements for Rel-19 NTN phase3 |
CATT |
| R4-2503535 |
On R19 NTN (e)RedCap RRM requirements |
Apple |
| R4-2503669 |
Discussion on RRM requirements of RedCap in Rel-19 NTN phase 3 |
Samsung |
| R4-2503793 |
Discussion on RRM requirements for RedCap NTN enhancement |
ZTECorporation,Sanechips |
| R4-2503904 |
Discussion on RRM requirements for RedCap UE in NTN |
Huawei, HiSilicon |
| R4-2504050 |
Discussion on RRM requirements on (e)RedCap for R19 NR NTN Phase 3 |
vivo |
| R4-2504112 |
Discussion on RedCap RRM requirements for NTN for NR Phase 3 |
Ericsson |
| R4-2504510 |
Discussion on requirements for RedCap support in NR NTN |
Nokia |
| R4-2504511 |
Draft CR38.133 Inter-RAT E-UTRAN in TN cell reselection for (e)RedCap over NR NTN |
Nokia |
| R4-2504530 |
RedCap for NTN |
Qualcomm Incorporated |
| 7.29.4.2 |
Other RRM requirements |
|
| R4-2503305 |
Discussion on other RRM core requirements in NTN for NR Phase 3 |
Xiaomi |
| R4-2503349 |
Discussion on other RRM requirements of R19 NR NTN |
OPPO |
| R4-2503386 |
Discussion on the RRM requirement for NTN phase3 |
CMCC |
| R4-2503437 |
Discussion on other RRM requirements for Rel-19 NTN phase3 |
CATT |
| R4-2503536 |
On R19 other NTN RRM requirements |
Apple |
| R4-2503670 |
Discussion on RRM requirements of other aspects in Rel-19 NTN phase 3 |
Samsung |
| R4-2503798 |
Discussion on RRM requirements for downlink coverage enhancement |
ZTECorporation,Sanechips |
| R4-2503905 |
Discussion on other RRM requirements for Rel-19 NTN |
Huawei, HiSilicon |
| R4-2504051 |
Discussion on RRM impacts on DL coverage for R19 NR NTN Phase 3 |
vivo |
| R4-2504111 |
Discussion on other RRM requirements for NTN for NR Phase 3 |
Ericsson |
| R4-2504447 |
Mobility aspects related to extended SSB periodicity in NR over NTN |
Nokia |
| R4-2504531 |
Downlink coverage enhancement for NTN |
Qualcomm Incorporated |
| 7.29.5 |
Moderator summary and conclusions |
|
| R4-2503631 |
Topic summary for [114bis][221] NR_NTN_Ph3_Part1 |
Moderator (CATT) |
| R4-2503632 |
Topic summary for [114bis][222] NR_NTN_Ph3_Part2 |
Moderator (Qualcomm) |
| R4-2504634 |
Topic summary for [114bis][309] NR_NTN_Ph3_General_UE_SAN_RF |
Moderator (Qualcomm) |
| R4-2504708 |
Way Forward for [114bis][309] NR_NTN_Ph3_General_UE_SAN_RF |
Qualcomm |
| R4-2504912 |
WF on RRM requirements for NR_NTN_Ph3_Part1 |
CATT |
| R4-2504913 |
WF on RRM requirements for NR_NTN_Ph3_Part2 |
Qualcomm |
| R4-2504967 |
Ad-hoc minutes on RRM requirements for NR_NTN_Ph3 |
Qualcomm, CATT |
| 7.30.1 |
General aspects |
|
| R4-2503716 |
Draft CR to TS 36.108: Correction of Regenerative Payload Figures |
NEC Europe Ltd, THALES |
| R4-2504715 |
Draft CR to TS 36.108: Correction of Regenerative Payload Figures |
NEC Europe Ltd, THALES, Huawei, CATT, Ericsson |
| 7.30.2 |
RF core requirements |
|
| R4-2503387 |
Discussion on the LS on TDM DMRS for 3.75kHz SCS OCC |
CMCC |
| R4-2503715 |
Discussion on feasibility of TDM DMRS for 3.75kHz SCS OCC |
LG Electronics Inc. |
| R4-2504067 |
OCC scheme on the RF requirements for IoT NTN |
Sony |
| R4-2504405 |
LS reply for IoT NTN |
Ericsson |
| R4-2504423 |
Discussion on the LS Reply regarding DMRS puncturing in NB-IoT over NTN |
Nokia |
| R4-2504465 |
Discussion on RF requirement impact for IoT NTN phase 3 |
MediaTek (Hefei) Inc. |
| R4-2504553 |
IoT NTN UL Capacity Enhancements |
Qualcomm Inc. |
| R4-2504556 |
On TDM DMRS for 3.75kHz SCS OCC for IoT NTN |
Huawei, HiSilicon |
| 7.30.3 |
RRM core requirements |
|
| R4-2503132 |
Discussion on RRM requirements for IoT NTN phase 3 |
MediaTek inc. |
| R4-2503133 |
DraftCR on timing requirement for IoT NTN phase 3 |
MediaTek inc. |
| R4-2503388 |
Discussion on the RRM requirement for IOT NTN phase3 |
CMCC |
| R4-2503871 |
Discussion on RRM impact for IoT NTN |
Huawei, HiSilicon |
| R4-2504110 |
Discussion on RRM requirements of Non-Terrestrial Networks (NTN) for Internet of Things (IoT) Phase 3 |
Ericsson |
| 7.30.4 |
Moderator summary and conclusions |
|
| R4-2503633 |
Topic summary for [114bis][223] IoT_NTN_Ph3 |
Moderator (MediaTek) |
| R4-2504640 |
Topic summary for [114bis][315] IoT_NTN_Ph3 |
Moderator (MediaTek) |
| R4-2504716 |
LS reply on TDM DMRS |
Sony |
| R4-2504717 |
Way Forward for [114bis][315] IoT_NTN_Ph3 |
MediaTek |
| R4-2504914 |
WF on RRM requirements for IoT_NTN_Ph3 |
MediaTek |
| 7.31 |
Introduction of IoT-NTN TDD mode |
|
| R4-2503200 |
Work plan for WID: introduction of IoT-NTN TDD mode |
Iridium Satellite LLC |
| 7.31.2 |
Band and system parameters (DL and UL channelization, channel bandwidth) |
|
| R4-2503744 |
draftCR to TS36.102 Introduction of IoT-NTN TDD band |
ZTE Corporation, Sanechips |
| 7.31.3 |
SAN RF requirements |
|
| R4-2503745 |
Discussion on SAN RF requirements for IoT-NTN TDD band |
ZTE Corporation, Sanechips |
| R4-2503746 |
draftCR to TS36.108 Introduction of IoT-NTN TDD band |
ZTE Corporation, Sanechips |
| R4-2504618 |
SAN RF requirements for NTN NB-IoT TDD |
THALES, Iridium Satellite LLC |
| 7.31.4 |
UE RF requirements |
|
| R4-2503564 |
Frequency error and UE regulatory requirements |
Qualcomm Incorporated |
| R4-2504619 |
UE RF requirements for NTN NB-IoT TDD |
THALES, Iridium Satellite LLC |
| 7.31.5 |
RRM core requirements |
|
| R4-2503134 |
Discussion on RRM requirements for IoT-NTN TDD mode |
MediaTek inc. |
| R4-2503799 |
Discussion on IoT NTN TDD mode |
ZTECorporation,Sanechips |
| R4-2503872 |
Discussion on RRM impact due to periodic pattern for IoT NTN |
Huawei, HiSilicon |
| R4-2504448 |
Discussion on IoT NTN TDD requirements |
Nokia |
| R4-2504529 |
RRM requirements for IoT NTN in TDD mode |
Qualcomm Incorporated |
| R4-2504615 |
RRM requirements for NTN NB-IoT TDD |
THALES, Iridium Satellite LLC |
| 7.31.6 |
Moderator summary and conclusions |
|
| R4-2503634 |
Topic summary for [114bis][224] IoT_NTN_TDD |
Moderator (Qualcomm) |
| R4-2504641 |
Topic summary for [114bis][316] IoT_NTN_TDD_UE_SAN_RF |
Moderator (Thales) |
| R4-2504719 |
Way Forward for [114bis][316] IoT_NTN_TDD_UE_SAN_RF |
Thales |
| R4-2504915 |
WF on RRM requirements for IoT_NTN_TDD |
Qualcomm |
| 8.2 |
R18 related |
|
| R4-2503360 |
Reply LS on AdditionalSpectrumEmission |
MediaTek Korea Inc. |
| R4-2503576 |
Reply LS on granularity definition of pdcch-RACH-AffectedBandsList-r18 |
Apple |
| R4-2503600 |
Reply LS on AdditionalSpectrumEmission |
LG Electronics |
| R4-2503610 |
Discussion on the question from RAN2 on R18 LTM |
MediaTek Inc. |
| R4-2503641 |
Reply LS to RAN2 on additionalSpectrumEmission in NR SL |
ZTE Corporation, Sanechips |
| R4-2503827 |
Discussion and reply LS on additionalSpectrumEmission on Sidelink |
vivo |
| R4-2503861 |
Discussion and draft Reply LS to RAN2 on granularity definition of pdcch-RACH-AffectedBandsList-r18 |
ZTE Corporation, Sanechips |
| R4-2503892 |
Reply LS on granularity definition of pdcch-RACH-AffectedBandsList-r18 |
Huawei, HiSilicon |
| R4-2504032 |
Discussion on measurement quantities for IoT NTN |
vivo |
| R4-2504033 |
Reply LS on measurement quantities for IoT NTN |
vivo |
| R4-2504351 |
Reply LS on granularity definition of pdcch-RACH-AffectedBandsList-r18 |
vivo |
| R4-2504424 |
Discussion on reply LS on measurement quantities for IoT NTN |
Ericsson |
| R4-2504444 |
(IoT_NTN_enh) Discussion on the LS Reply regarding measurement quantities in NB-IoT over NTN (R1-2501512) |
Nokia |
| R4-2504471 |
LS reply to RAN2 on granularity definition of pdcch-RACH-AffectedBandsList-r18 |
Nokia |
| R4-2504523 |
Reply LS to RAN2 on granularity definition of pdcch-RACH-AffectedBandsList-r18 |
Qualcomm Incorporated |
| R4-2504718 |
Reply LS on measurement quantities for IoT NTN |
vivo |
| R4-2505217 |
Reply LS to RAN2 on additionalSpectrumEmission |
ZTE Corporation, Sanechips |
| 8.3 |
R17, R15 and R16 related |
|
| R4-2504407 |
Discussion on reply LS on measurement quantities for IoT NTN |
Ericsson |
| 8.4 |
Moderator summary and conclusions |
|
| R4-2503635 |
Topic summary for [114bis][225] Reply_LS |
Moderator (Apple) |
| R4-2504655 |
Topic summary for [114bis][330] LS_BDaT |
Moderator (Qualcomm) |
| R4-2504690 |
Topic summary for [114bis][132] NR_reply_LS_UE_RF |
Moderator(Apple) |
| 9 |
RAN task and other topics |
|
| R4-2504125 |
Progress update and next steps for the CA database |
Nokia |
| 9.1 |
Framework simplification for co-location/co-existence requirements (RP-243288) |
|
| R4-2503233 |
On RAN task to work on framework simplification for co-location/co-existence requirements |
Nokia |
| R4-2503462 |
Further discussion on framework simplification for co-location/co-existence requirements |
CATT |
| R4-2503463 |
Draft CR for 38.104, on framework simplification for co-location/co-existence requirement |
CATT |
| R4-2503464 |
Draft CR for 38.106, on framework simplification for co-location/co-existence requirement |
CATT |
| R4-2503465 |
Draft CR for 38.174, on framework simplification for co-location/co-existence requirement |
CATT |
| R4-2503727 |
Draft CR to TS 38.104: Introduction of new requirement structure for transmitter spurious emission in subclause 6.6.5.2.3 and subclause 6.6.5.2.4 |
Ericsson |
| R4-2503728 |
Draft CR to TS 38.141-2: Introduction of new requirement structure for transmitter spurious emission in sub-clause 6.7.5.4.5 and sub-clause 6.7.5.5.5 |
Ericsson |
| R4-2503729 |
On the topic of BS RF specification structure improvements |
Ericsson |
| R4-2503730 |
Draft CR to TS 38.141-1: Introduction of new requirement structure for transmitter spurious emission in sub-clause 6.6.5.5.1.3 and sub-clause 6.6.5.5.1.4 |
Ericsson |
| R4-2504366 |
Discussion on the simplification for BS spec |
ZTE Corporation, Sanechips |
| R4-2504498 |
Some considerations on CA framework database |
ZTE Corporation, Sanechips |
| R4-2504572 |
draftCR to 38.104: on framework simplification for co-location/co-existence requirements |
Nokia |
| R4-2504573 |
draftCR to 38.141-1: on framework simplification for co-location/co-existence requirements |
Nokia |
| R4-2504595 |
Further discussion on the framework simplification for co-location/co-existence requirements |
Huawei, HiSilicon |
| R4-2504656 |
Topic summary for [114bis][331] BSRF_Simplify_CoLo_Coex |
Moderator (Ericsson) |
| R4-2504741 |
Way Forward for [114bis][331] BSRF_Simplify_CoLo_Coex |
Ericsson |
| 9.2 |
Principle of selected specification series in case of spectrum sharing by multiple RATs (related to approval of RP-250611) |
|
| R4-2504408 |
Specification impact on spectrum sharing by multiple RATs |
Ericsson |
| 10 |
New or revised WID/SID |
|
| R4-2503718 |
WF on 200 MHz channel bandwidth |
KDDI, China Unicom, China Telecom, BT, Bouygues Telecom, Deutsche Telekom, KPN, Vodafone, Orange, Odido, Telefonica, Telenor, TIM, Telia Company, Spark NZ, Jio Platforms(JPL), Telstra, NTT Docomo, SoftBank, CKH IOD UK LTD, Ericsson, Huawei |
| R4-2503720 |
Motivation on supporting Intra-band non-collocated EN-DC/NR-CA deployment in Release 20 (Type 3 UE for handheld) |
KDDI, NTT Docomo, SoftBank, KT, LG Uplus |
| R4-2503721 |
Observation on UE simulation assumption for MPR, A-MPR |
KDDI Corporation |
| R4-2503725 |
Considerations on Rel-20 BS RF package objectives |
Ericsson |
| R4-2503847 |
New WID on New Power Class and enhanced requirements for NR and IoT NTN |
vivo |
| R4-2504077 |
MediaTek Views on Rel-20 RAN4 5G-A scope |
MediaTek inc. |
| R4-2504367 |
Discussion on Rel-20 BS RF enhancement |
ZTE Corporation, Sanechips |
| R4-2504375 |
Views on Rel-20 RRM topics |
Ericsson |
| 11 |
Any other business |
|
| R4-2503567 |
6G specification format modernization: towards Automation-Native |
Nokia |
| R4-2504770 |
(reserved) |
BDaT Session |
| R4-2504771 |
(reserved) |
BDaT Session |
| R4-2504772 |
(reserved) |
BDaT Session |
| R4-2504773 |
(reserved) |
BDaT Session |
| R4-2504774 |
(reserved) |
BDaT Session |
| R4-2504775 |
(reserved) |
BDaT Session |
| R4-2504776 |
(reserved) |
BDaT Session |
| R4-2504777 |
(reserved) |
BDaT Session |
| R4-2504778 |
(reserved) |
BDaT Session |
| R4-2504779 |
(reserved) |
BDaT Session |
| R4-2504780 |
(reserved) |
BDaT Session |
| R4-2504781 |
(reserved) |
BDaT Session |
| R4-2504782 |
(reserved) |
BDaT Session |
| R4-2504783 |
(reserved) |
BDaT Session |
| R4-2504784 |
(reserved) |
BDaT Session |
| R4-2504785 |
(reserved) |
BDaT Session |
| R4-2504786 |
(reserved) |
BDaT Session |
| R4-2504787 |
(reserved) |
BDaT Session |
| R4-2504788 |
(reserved) |
BDaT Session |
| R4-2504789 |
(reserved) |
BDaT Session |
| R4-2504790 |
(reserved) |
BDaT Session |
| R4-2504791 |
(reserved) |
BDaT Session |
| R4-2504792 |
(reserved) |
BDaT Session |
| R4-2504793 |
(reserved) |
BDaT Session |
| R4-2504794 |
(reserved) |
BDaT Session |
| R4-2504795 |
(reserved) |
BDaT Session |
| R4-2504796 |
(reserved) |
BDaT Session |
| R4-2504797 |
(reserved) |
BDaT Session |
| R4-2504798 |
(reserved) |
BDaT Session |
| R4-2504799 |
(reserved) |
BDaT Session |
| R4-2504800 |
(reserved) |
BDaT Session |
| R4-2504801 |
(reserved) |
BDaT Session |
| R4-2504802 |
(reserved) |
BDaT Session |
| R4-2504803 |
(reserved) |
BDaT Session |
| R4-2504804 |
(reserved) |
BDaT Session |
| R4-2504805 |
(reserved) |
BDaT Session |
| R4-2504806 |
(reserved) |
BDaT Session |
| R4-2504807 |
(reserved) |
BDaT Session |
| R4-2504808 |
(reserved) |
BDaT Session |
| R4-2504809 |
(reserved) |
BDaT Session |
| R4-2504810 |
(reserved) |
BDaT Session |
| R4-2504811 |
(reserved) |
BDaT Session |
| R4-2504812 |
(reserved) |
BDaT Session |
| R4-2504813 |
(reserved) |
BDaT Session |
| R4-2504814 |
(reserved) |
BDaT Session |
| R4-2504815 |
(reserved) |
BDaT Session |
| R4-2504816 |
(reserved) |
BDaT Session |
| R4-2504817 |
(reserved) |
BDaT Session |
| R4-2504818 |
(reserved) |
BDaT Session |
| R4-2504819 |
(reserved) |
BDaT Session |
| R4-2504820 |
(reserved) |
BDaT Session |
| R4-2504821 |
(reserved) |
BDaT Session |
| R4-2504822 |
(reserved) |
BDaT Session |
| R4-2504823 |
(reserved) |
BDaT Session |
| R4-2504824 |
(reserved) |
BDaT Session |
| R4-2504825 |
(reserved) |
BDaT Session |
| R4-2504826 |
(reserved) |
BDaT Session |
| R4-2504827 |
(reserved) |
BDaT Session |
| R4-2504828 |
(reserved) |
BDaT Session |
| R4-2504829 |
(reserved) |
BDaT Session |
| R4-2504830 |
(reserved) |
BDaT Session |
| R4-2504831 |
(reserved) |
BDaT Session |
| R4-2504832 |
(reserved) |
BDaT Session |
| R4-2504833 |
(reserved) |
BDaT Session |
| R4-2504834 |
(reserved) |
BDaT Session |
| R4-2504835 |
(reserved) |
BDaT Session |
| R4-2504836 |
(reserved) |
BDaT Session |
| R4-2504837 |
(reserved) |
BDaT Session |
| R4-2504838 |
(reserved) |
BDaT Session |
| R4-2504839 |
(reserved) |
BDaT Session |
| R4-2504840 |
(reserved) |
BDaT Session |
| R4-2504841 |
(reserved) |
BDaT Session |
| R4-2504842 |
(reserved) |
BDaT Session |
| R4-2504843 |
(reserved) |
BDaT Session |
| R4-2504844 |
(reserved) |
BDaT Session |
| R4-2504845 |
(reserved) |
BDaT Session |
| R4-2504846 |
(reserved) |
BDaT Session |
| R4-2504847 |
(reserved) |
BDaT Session |
| R4-2504848 |
(reserved) |
BDaT Session |
| R4-2504849 |
(reserved) |
BDaT Session |
| R4-2504850 |
(reserved) |
BDaT Session |
| R4-2504851 |
(reserved) |
BDaT Session |
| R4-2504852 |
(reserved) |
BDaT Session |
| R4-2504853 |
(reserved) |
BDaT Session |
| R4-2504854 |
(reserved) |
BDaT Session |
| R4-2504855 |
(reserved) |
BDaT Session |
| R4-2504856 |
(reserved) |
BDaT Session |
| R4-2504857 |
(reserved) |
BDaT Session |
| R4-2504858 |
(reserved) |
BDaT Session |
| R4-2504859 |
(reserved) |
BDaT Session |
| R4-2504860 |
(reserved) |
BDaT Session |
| R4-2504861 |
(reserved) |
BDaT Session |
| R4-2504862 |
(reserved) |
BDaT Session |
| R4-2504863 |
(reserved) |
BDaT Session |
| R4-2504864 |
(reserved) |
BDaT Session |
| R4-2504865 |
(reserved) |
BDaT Session |
| R4-2504866 |
(reserved) |
BDaT Session |
| R4-2504867 |
(reserved) |
BDaT Session |
| R4-2504868 |
(reserved) |
BDaT Session |
| R4-2504869 |
(reserved) |
BDaT Session |
| R4-2504870 |
(reserved) |
BDaT Session |
| R4-2504871 |
(reserved) |
BDaT Session |
| R4-2504872 |
(reserved) |
BDaT Session |
| R4-2504873 |
(reserved) |
BDaT Session |
| R4-2504874 |
(reserved) |
BDaT Session |
| R4-2504875 |
(reserved) |
BDaT Session |
| R4-2504876 |
(reserved) |
BDaT Session |
| R4-2504877 |
(reserved) |
BDaT Session |
| R4-2504878 |
(reserved) |
BDaT Session |
| R4-2504879 |
(reserved) |
BDaT Session |
| R4-2504880 |
(reserved) |
BDaT Session |
| R4-2504881 |
(reserved) |
BDaT Session |
| R4-2504882 |
(reserved) |
BDaT Session |
| R4-2504883 |
(reserved) |
BDaT Session |
| R4-2504884 |
(reserved) |
BDaT Session |
| R4-2504885 |
(reserved) |
BDaT Session |
| R4-2504886 |
(reserved) |
BDaT Session |
| R4-2504887 |
(reserved) |
BDaT Session |
| R4-2504888 |
(reserved) |
BDaT Session |
| R4-2504889 |
(reserved) |
BDaT Session |
| R4-2504890 |
(reserved) |
BDaT Session |
| R4-2504891 |
(reserved) |
BDaT Session |
| 12 |
Close of the meeting |
|
| R4-2504973 |
(reserved) |
RRM Session |
| R4-2504974 |
(reserved) |
RRM Session |
| R4-2504975 |
(reserved) |
RRM Session |
| R4-2504976 |
(reserved) |
RRM Session |
| R4-2504977 |
(reserved) |
RRM Session |
| R4-2504978 |
(reserved) |
RRM Session |
| R4-2504979 |
(reserved) |
RRM Session |
| R4-2504980 |
(reserved) |
RRM Session |
| R4-2504981 |
(reserved) |
RRM Session |
| R4-2504982 |
(reserved) |
RRM Session |
| R4-2504983 |
(reserved) |
RRM Session |
| R4-2504984 |
(reserved) |
RRM Session |
| R4-2504985 |
(reserved) |
RRM Session |
| R4-2504986 |
(reserved) |
RRM Session |
| R4-2504987 |
(reserved) |
RRM Session |
| R4-2504988 |
(reserved) |
RRM Session |
| R4-2504989 |
(reserved) |
RRM Session |
| R4-2504990 |
(reserved) |
RRM Session |
| R4-2504991 |
(reserved) |
RRM Session |
| R4-2504992 |
(reserved) |
RRM Session |
| R4-2504993 |
(reserved) |
RRM Session |
| R4-2504994 |
(reserved) |
RRM Session |
| R4-2504995 |
(reserved) |
RRM Session |
| R4-2504996 |
(reserved) |
RRM Session |
| R4-2504997 |
(reserved) |
RRM Session |
| R4-2504998 |
(reserved) |
RRM Session |
| R4-2504999 |
(reserved) |
RRM Session |
| R4-2505000 |
(reserved) |
RRM Session |
| R4-2505001 |
(reserved) |
RRM Session |
| R4-2505002 |
(reserved) |
RRM Session |
| R4-2505003 |
(reserved) |
RRM Session |
| R4-2505004 |
(reserved) |
RRM Session |
| R4-2505005 |
(reserved) |
RRM Session |
| R4-2505006 |
(reserved) |
RRM Session |
| R4-2505007 |
(reserved) |
RRM Session |
| R4-2505008 |
(reserved) |
RRM Session |
| R4-2505009 |
(reserved) |
RRM Session |
| R4-2505010 |
(reserved) |
RRM Session |
| R4-2505011 |
(reserved) |
RRM Session |
| R4-2505012 |
(reserved) |
RRM Session |
| R4-2505013 |
(reserved) |
RRM Session |
| R4-2505014 |
(reserved) |
RRM Session |
| R4-2505015 |
(reserved) |
RRM Session |
| R4-2505016 |
(reserved) |
RRM Session |
| R4-2505017 |
(reserved) |
RRM Session |
| R4-2505018 |
(reserved) |
RRM Session |
| R4-2505019 |
(reserved) |
RRM Session |
| R4-2505020 |
(reserved) |
RRM Session |
| R4-2505021 |
(reserved) |
RRM Session |
| R4-2505022 |
(reserved) |
RRM Session |
| R4-2505023 |
(reserved) |
RRM Session |
| R4-2505024 |
(reserved) |
RRM Session |
| R4-2505025 |
(reserved) |
RRM Session |
| R4-2505026 |
(reserved) |
RRM Session |
| R4-2505027 |
(reserved) |
RRM Session |
| R4-2505028 |
(reserved) |
RRM Session |
| R4-2505029 |
(reserved) |
RRM Session |
| R4-2505030 |
(reserved) |
RRM Session |
| R4-2505031 |
(reserved) |
RRM Session |
| R4-2505032 |
(reserved) |
RRM Session |
| R4-2505033 |
(reserved) |
RRM Session |
| R4-2505034 |
(reserved) |
RRM Session |
| R4-2505035 |
(reserved) |
RRM Session |
| R4-2505036 |
(reserved) |
RRM Session |
| R4-2505037 |
(reserved) |
RRM Session |
| R4-2505038 |
(reserved) |
RRM Session |
| R4-2505039 |
(reserved) |
RRM Session |
| R4-2505040 |
(reserved) |
RRM Session |
| R4-2505041 |
(reserved) |
RRM Session |
| R4-2505042 |
(reserved) |
RRM Session |
| R4-2505043 |
(reserved) |
RRM Session |
| R4-2505044 |
(reserved) |
RRM Session |
| R4-2505045 |
(reserved) |
RRM Session |
| R4-2505046 |
(reserved) |
RRM Session |
| R4-2505047 |
(reserved) |
RRM Session |
| R4-2505048 |
(reserved) |
RRM Session |
| R4-2505049 |
(reserved) |
RRM Session |
| R4-2505050 |
(reserved) |
RRM Session |
| R4-2505051 |
(reserved) |
RRM Session |
| R4-2505052 |
(reserved) |
RRM Session |
| R4-2505053 |
(reserved) |
RRM Session |
| R4-2505054 |
(reserved) |
RRM Session |
| R4-2505055 |
(reserved) |
RRM Session |
| R4-2505056 |
(reserved) |
RRM Session |
| R4-2505057 |
(reserved) |
RRM Session |
| R4-2505058 |
(reserved) |
RRM Session |
| R4-2505059 |
(reserved) |
RRM Session |
| R4-2505060 |
(reserved) |
RRM Session |
| R4-2505061 |
(reserved) |
RRM Session |
| R4-2505062 |
(reserved) |
RRM Session |
| R4-2505063 |
(reserved) |
RRM Session |
| R4-2505064 |
(reserved) |
RRM Session |
| R4-2505065 |
(reserved) |
RRM Session |
| R4-2505066 |
(reserved) |
RRM Session |
| R4-2505067 |
(reserved) |
RRM Session |
| R4-2505068 |
(reserved) |
RRM Session |
| R4-2505069 |
(reserved) |
RRM Session |
| R4-2505070 |
(reserved) |
RRM Session |
| R4-2505071 |
(reserved) |
RRM Session |
| R4-2505072 |
(reserved) |
RRM Session |
| R4-2505073 |
(reserved) |
RRM Session |
| R4-2505074 |
(reserved) |
RRM Session |
| R4-2505075 |
(reserved) |
RRM Session |
| R4-2505076 |
(reserved) |
RRM Session |
| R4-2505077 |
(reserved) |
RRM Session |
| R4-2505078 |
(reserved) |
RRM Session |
| R4-2505079 |
(reserved) |
RRM Session |
| R4-2505080 |
(reserved) |
RRM Session |
| R4-2505081 |
(reserved) |
RRM Session |
| R4-2505082 |
(reserved) |
RRM Session |
| R4-2505083 |
(reserved) |
RRM Session |
| R4-2505084 |
(reserved) |
RRM Session |
| R4-2505085 |
(reserved) |
RRM Session |
| R4-2505086 |
(reserved) |
RRM Session |
| R4-2505087 |
(reserved) |
RRM Session |
| R4-2505088 |
(reserved) |
RRM Session |
| R4-2505089 |
(reserved) |
RRM Session |
| R4-2505090 |
(reserved) |
RRM Session |
| R4-2505091 |
(reserved) |
RRM Session |
| R4-2505237 |
(reserved) |
Main Session |
| R4-2505238 |
(reserved) |
Main Session |
| R4-2505239 |
(reserved) |
Main Session |
| R4-2505240 |
(reserved) |
Main Session |
| R4-2505241 |
(reserved) |
Main Session |
| R4-2505242 |
(reserved) |
Main Session |
| R4-2505243 |
(reserved) |
Main Session |
| R4-2505244 |
(reserved) |
Main Session |
| R4-2505245 |
(reserved) |
Main Session |
| R4-2505246 |
(reserved) |
Main Session |
| R4-2505247 |
(reserved) |
Main Session |
| R4-2505248 |
(reserved) |
Main Session |
| R4-2505249 |
(reserved) |
Main Session |
| R4-2505250 |
(reserved) |
Main Session |
| R4-2505251 |
(reserved) |
Main Session |
| R4-2505252 |
(reserved) |
Main Session |
| R4-2505253 |
(reserved) |
Main Session |
| R4-2505254 |
(reserved) |
Main Session |
| R4-2505255 |
(reserved) |
Main Session |
| R4-2505256 |
(reserved) |
Main Session |
| R4-2505257 |
(reserved) |
Main Session |
| R4-2505258 |
(reserved) |
Main Session |
| R4-2505259 |
(reserved) |
Main Session |
| R4-2505260 |
(reserved) |
Main Session |
| R4-2505261 |
(reserved) |
Main Session |
| R4-2505262 |
(reserved) |
Main Session |
| R4-2505263 |
(reserved) |
Main Session |
| R4-2505264 |
(reserved) |
Main Session |
| R4-2505265 |
(reserved) |
Main Session |
| R4-2505266 |
(reserved) |
Main Session |
| R4-2505267 |
(reserved) |
Main Session |
| R4-2505268 |
(reserved) |
Main Session |
| R4-2505269 |
(reserved) |
Main Session |
| R4-2505270 |
(reserved) |
Main Session |
| R4-2505271 |
(reserved) |
Main Session |
| R4-2505272 |
(reserved) |
Main Session |
| R4-2505273 |
(reserved) |
Main Session |
| R4-2505274 |
(reserved) |
Main Session |
| R4-2505275 |
(reserved) |
Main Session |
| R4-2505276 |
(reserved) |
Main Session |
| R4-2505277 |
(reserved) |
Main Session |
| R4-2505278 |
(reserved) |
Main Session |
| R4-2505279 |
(reserved) |
Main Session |
| R4-2505280 |
(reserved) |
Main Session |
| R4-2505281 |
(reserved) |
Main Session |
| R4-2505282 |
(reserved) |
Main Session |
| R4-2505283 |
(reserved) |
Main Session |
| R4-2505284 |
(reserved) |
Main Session |
| R4-2505285 |
(reserved) |
Main Session |
| R4-2505286 |
(reserved) |
Main Session |
| R4-2505287 |
(reserved) |
Main Session |
| R4-2505288 |
(reserved) |
Main Session |
| R4-2505289 |
(reserved) |
Main Session |
| R4-2505290 |
(reserved) |
Main Session |
| R4-2505291 |
(reserved) |
Main Session |
| R4-2505292 |
Special gift for Xizeng - Part 1 |
Huawei, HiSilicon |
| R4-2505293 |
Special gift for Xizeng - Part 2 |
Huawei, HiSilicon |